Triple
T34780422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermes communication systems |
E1002641
|
entity |
| Predicate | authorUniverseCreator |
P115764
|
FINISHED |
| Object | Andy Weir |
E197784
|
NE 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: Andy Weir | Statement: [Hermes communication systems, authorUniverseCreator, Andy Weir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorUniverseCreator Context triple: [Hermes communication systems, authorUniverseCreator, Andy Weir]
-
A.
fictionalUniverseAuthor
chosen
Indicates that an author is the creator or primary writer responsible for a given fictional universe.
-
B.
fictionalUniverseOwner
Indicates that one entity is the creator, rights holder, or controlling owner of a particular fictional universe or setting.
-
C.
createdInUniverseBy
Indicates that something was brought into existence within a particular fictional or conceptual universe by a specific creator or originating agent.
-
D.
creatorOfUniverse
Indicates that an entity is responsible for bringing the universe into existence or causing its creation.
-
E.
creativeUniverseOwner
Indicates that an entity holds ownership or authoritative control over a creative universe or fictional world.
- F. None of above.
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_69f76db30a108190bb57ca95b873e5bb |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a376642e6708190aa64aa53544c7350 |
completed | June 21, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 3, 2026, 3:59 p.m.