Triple
T2601016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maitreya |
E58341
|
entity |
| Predicate | willBeBornAs |
P39533
|
FINISHED |
| Object | Human being in the future |
—
|
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: Human being in the future | Statement: [Maitreya, willBeBornAs, Human being in the future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: willBeBornAs Context triple: [Maitreya, willBeBornAs, Human being in the future]
-
A.
wasBornInto
Indicates that an entity entered existence as a member of a particular family, social group, or circumstance at birth.
-
B.
gaveBirthTo
Indicates that one entity is the biological parent who delivered another entity as offspring.
-
C.
announcesConceptionOf
Indicates that one entity publicly declares or makes known the beginning or creation of another entity (such as a project, idea, or initiative).
-
D.
birthEmpire
Indicates that an entity was born within the territory or jurisdiction of a specified empire.
-
E.
birthType
Indicates the manner or method by which a birth occurred or was brought about.
- 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_69ab4ac14040819098b13f4a27d5c8ff |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd4587014819089f78e93adf2144c |
completed | March 7, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69abd0d4e8648190b612eb09aa085451 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1c7b6e48190be9a0c31069df797 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:49 p.m.