Triple
T24248937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archippe |
E603458
|
entity |
| Predicate | hasUncertainGenealogy |
P86190
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Archippe, hasUncertainGenealogy, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUncertainGenealogy Context triple: [Archippe, hasUncertainGenealogy, true]
-
A.
hasUncertainParentage
chosen
Indicates that the parent or parents of an entity are unknown, disputed, or not reliably established.
-
B.
hasUncertainOrigin
Indicates that the origin or source of an entity, event, or information is unknown, unclear, or not reliably established.
-
C.
hasUncertainHistoricBasis
Indicates that the historical foundation or authenticity of the related fact, event, or relationship is doubtful, disputed, or not firmly established.
-
D.
hasGenealogy
Indicates that one entity possesses or is associated with the genealogical record, lineage, or ancestry information of another entity.
-
E.
hasUncertainOffspring
Indicates that an entity is associated with offspring whose existence, identity, or parentage is not fully certain or confirmed.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b87d03c8190a38ca0c0b65ce6fc |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:04 a.m.