Triple
T19941326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartoi |
E479313
|
entity |
| Predicate | survivorsFunction |
P137934
|
FINISHED |
| Object | founders of Theban aristocratic houses |
—
|
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: founders of Theban aristocratic houses | Statement: [Spartoi, survivorsFunction, founders of Theban aristocratic houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivorsFunction Context triple: [Spartoi, survivorsFunction, founders of Theban aristocratic houses]
-
A.
survivalFunction
Indicates the probability that an entity or system continues to exist or function without failure beyond a given point in time.
-
B.
survivesBy
Indicates that one entity continues to live or exist after another entity has died or ceased to exist.
-
C.
survivesFor
Indicates that one entity continues to exist, endure, or remain functional for a specified duration or period.
-
D.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
E.
survivesWith
Indicates that one entity continues to live, endure, or remain viable in the presence, context, or company of another entity.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6318848190a1dd3e0a6fea3fe2 |
completed | April 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.