Triple
T29661685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Top Toys |
E750423
|
entity |
| Predicate | inUniverseBrand |
P133890
|
FINISHED |
| Object | Big Top Toys |
—
|
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 Top Toys | Statement: [Big Top Toys, inUniverseBrand, Big Top Toys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseBrand Context triple: [Big Top Toys, inUniverseBrand, Big Top Toys]
-
A.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
B.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
C.
inUniverseMaterial
Indicates that something is made of or composed from a material that exists within a specified fictional or conceptual universe.
-
D.
inUniverseUse
Indicates that something is used or occurs within a particular fictional or conceptual universe, as opposed to in the real world or another setting.
-
E.
isBrand
chosen
Indicates that one entity functions as the commercial brand or label associated with another entity.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 6:58 p.m.