Triple
T36132840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Man Beneath |
E1045068
|
entity |
| Predicate | hasStarSystemRole |
P201874
|
FINISHED |
| Object | leading man vehicle for Sessue Hayakawa |
—
|
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: leading man vehicle for Sessue Hayakawa | Statement: [The Man Beneath, hasStarSystemRole, leading man vehicle for Sessue Hayakawa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStarSystemRole Context triple: [The Man Beneath, hasStarSystemRole, leading man vehicle for Sessue Hayakawa]
-
A.
hasStarSystem
Indicates that an entity possesses, contains, or is associated with a particular star system.
-
B.
hasStandardStarRole
Indicates that an entity holds a primary or typical starring role in relation to another entity.
-
C.
isInGalacticSystem
Indicates that one astronomical object is located within or belongs to a particular galactic system.
-
D.
roleOnGalactica
Indicates the specific position, duty, or function an entity holds aboard the Battlestar Galactica.
-
E.
hasGalaxyGroupRole
Indicates that an entity holds a specific role or function within a galaxy group.
- 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_69f76e36a4508190b5bfc8f594272a4c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a002dd4066c8190945a09ed82f44f3f |
completed | May 10, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_6a002b141f4081909999e14988105f3a |
completed | May 10, 2026, 6:52 a.m. |
| PDg | Predicate description generation | batch_6a002dd3294881909e860157fc459a85 |
completed | May 10, 2026, 7:03 a.m. |
Created at: May 3, 2026, 4:08 p.m.