Triple
T37918649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treelo |
E945893
|
entity |
| Predicate | isCharacterInUniverse |
P133542
|
FINISHED |
| Object | Big Blue House |
—
|
NE NERFINISHED |
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: Big Blue House | Statement: [Treelo, isCharacterInUniverse, Big Blue House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCharacterInUniverse Context triple: [Treelo, isCharacterInUniverse, Big Blue House]
-
A.
inUniverseCharacter
chosen
Indicates that a character exists within, and is part of, the fictional universe or continuity defined by a particular work or franchise.
-
B.
isSetInFictionalUniverse
Indicates that a narrative work takes place within a specific fictional universe or setting.
-
C.
activeInFictionalUniverse
Indicates that an entity participates, operates, or has a role within a specified fictional universe or setting.
-
D.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
E.
isCharacterInWork
Indicates that a particular character appears in or is part of a specified creative work (such as a book, film, or game).
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.