Triple
T4649053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arete |
E102243
|
entity |
| Predicate | in-universeStatus |
P58920
|
FINISHED |
| Object | honored by her people |
—
|
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: honored by her people | Statement: [Arete, in-universeStatus, honored by her people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: in-universeStatus Context triple: [Arete, in-universeStatus, honored by her people]
-
A.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
B.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
C.
inUniverseOrigin
Indicates that one entity originates from, or has its source within, the fictional universe or setting defined by another entity.
-
D.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
E.
awardedInUniverse
Indicates that an award or honor is given within the context or setting of a particular fictional or defined universe.
- 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_69bd43d71a308190afea7280841b0de8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6632708c8190b627d99363ab062c |
completed | March 20, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69bd620fc5e081908325ac8e6a6384ab |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd663092cc81909308f89ee1a417e4 |
completed | March 20, 2026, 3:22 p.m. |
Created at: March 20, 2026, 1:14 p.m.