Triple
T34988819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titans Tower Island |
E1009325
|
entity |
| Predicate | hasStatusInStories |
P132213
|
FINISHED |
| Object | sometimes destroyed and rebuilt |
—
|
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: sometimes destroyed and rebuilt | Statement: [Titans Tower Island, hasStatusInStories, sometimes destroyed and rebuilt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatusInStories Context triple: [Titans Tower Island, hasStatusInStories, sometimes destroyed and rebuilt]
-
A.
teamStatusInStory
chosen
Indicates the status or role a team holds within the context of a particular story or narrative.
-
B.
hasTimeInStory
Indicates that a story element, event, or entity occurs or is present during a specific time or time interval within the narrative.
-
C.
storyStatus
Indicates the current state or phase of a story within its lifecycle (e.g., planned, in progress, completed, or archived).
-
D.
hasStaffTypeInStory
Indicates that a story involves or is associated with a particular type or category of staff.
-
E.
isStoried
Indicates that something has a rich history, reputation, or legacy built up over time, often marked by notable events or traditions.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffc7b4c7f88190b6357a44e7f0940f |
completed | May 9, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69ffc755f09c8190995ca00d97336988 |
completed | May 9, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.