Triple
T518699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddington–Finkelstein coordinates |
E10764
|
entity |
| Predicate | metricSignature |
P15342
|
FINISHED |
| Object | (-,+,+,+) |
—
|
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: (-,+,+,+) | Statement: [Eddington–Finkelstein coordinates, metricSignature, (-,+,+,+)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metricSignature Context triple: [Eddington–Finkelstein coordinates, metricSignature, (-,+,+,+)]
-
A.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
B.
signatureStyle
Indicates the characteristic way in which an entity typically signs its name or marks documents, distinguishing its unique signing pattern or format.
-
C.
signatureEvent
Indicates an event in which an entity formally signs or authorizes something, such as a document, agreement, or record.
-
D.
signatureImage
Indicates that an entity has an associated image that visually represents its signature.
-
E.
hasSignatureVisualStyle
Indicates that an entity is characterized by a distinctive and recognizable visual style that sets it apart from others.
- F. None of above. chosen
Provenance (4 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f19ee6748190916603ef3a9e27f3 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f0151e8c81909a82b58ac0515eba |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f1137e948190838303cdaa757a5a |
completed | Feb. 28, 2026, 1:43 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.