Triple
T15661774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minkowski metric η_{μν} |
E376582
|
entity |
| Predicate | usedAsBackgroundIn |
P98
|
FINISHED |
| Object | linearized gravity |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: linearized gravity | Statement: [Minkowski metric η_{μν}, usedAsBackgroundIn, linearized gravity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsBackgroundIn
Context triple: [Minkowski metric η_{μν}, usedAsBackgroundIn, linearized gravity]
-
A.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
B.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
usedAsLocationIn
Indicates that something serves as the setting or place where another event, action, or situation occurs.
-
D.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
alsoUsedIn
Indicates that something is additionally employed, applied, or present in another context, setting, or use case beyond the primary one.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f0e2668819092e52712cddd0721 |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.