Triple
T8989363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huni |
E214748
|
entity |
| Predicate | hasUncertainParentage |
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: [Huni, hasUncertainParentage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUncertainParentage Context triple: [Huni, hasUncertainParentage, true]
-
A.
hasPossibleFather
Indicates a relationship where a given individual may be the father of another, but this parentage is not confirmed.
-
B.
hasUncertainOrigin
Indicates that the origin or source of an entity, event, or information is unknown, unclear, or not reliably established.
-
C.
possibleMother
Indicates that one entity could be the biological or adoptive mother of another, but this relationship is uncertain or not definitively established.
-
D.
hasMotherOrigin
Indicates that an entity’s origin, source, or lineage is derived from or attributed to a mother entity.
-
E.
hasUncertainNature
Indicates that the nature, status, or characteristics of the relationship or situation are not clearly defined, known, or determined.
- 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_69ca839f76bc8190a4b7123cdd682199 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc687205c88190a4cdf12ee2cdfd14 |
completed | April 1, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5febd0a08190b2de6fb422343001 |
completed | March 31, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:04 p.m.