Triple
T32060531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hall of Everything |
E818734
|
entity |
| Predicate | targetUsersInStory |
P149750
|
FINISHED |
| Object | new souls |
—
|
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: new souls | Statement: [Hall of Everything, targetUsersInStory, new souls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetUsersInStory Context triple: [Hall of Everything, targetUsersInStory, new souls]
-
A.
targetParticipantsInStory
Indicates that certain participants are the intended or primary focus within the context of a story or narrative.
-
B.
targetConsumerInStory
Indicates that a specified consumer is the intended or focal target within the context of a particular story or narrative.
-
C.
ownerInStory
Indicates that one entity is the owner of another entity within the context or narrative of a specific story.
-
D.
primaryUserInStory
chosen
Indicates that a particular user is the main or central user involved in the context of a given story.
-
E.
networkAffiliationInStory
Indicates that, within the context of a story, an entity is affiliated with or belongs to a particular network (such as a media, broadcast, or organizational network).
- F. None of above.
Provenance (3 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: May 1, 2026, 12:21 a.m.