Triple
T669707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo |
E12942
|
entity |
| Predicate | twinStatus |
P2516
|
FINISHED |
| Object | twin brother of Artemis |
—
|
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: twin brother of Artemis | Statement: [Apollo, twinStatus, twin brother of Artemis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: twinStatus Context triple: [Apollo, twinStatus, twin brother of Artemis]
-
A.
hasTwin
chosen
Indicates that one entity is a twin of another, sharing the same birth event or time with a sibling.
-
B.
hasTwinTown
Indicates that two towns or cities are officially paired in a twinning relationship, typically for cultural, social, or economic exchange.
-
C.
hasTwinActors
Indicates that two or more actors share a twin relationship, typically portraying twin characters or being treated as twins within a given context.
-
D.
twinCity
Indicates that two cities are officially recognized as twin (or sister) cities, typically signifying a formal partnership for cultural, economic, or social exchange.
-
E.
sibling
Indicates that two entities share at least one parent, making them brothers or sisters to each other.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49ffbe09881909b547a52a6b34c7f |
completed | March 1, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69a49d18942c819083b3d1887e505900 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.