Triple
T15355676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lego Friends |
E367164
|
entity |
| Predicate | notableSetFeature |
P46274
|
FINISHED |
| Object | detailed buildings |
—
|
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: detailed buildings | Statement: [Lego Friends, notableSetFeature, detailed buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSetFeature Context triple: [Lego Friends, notableSetFeature, detailed buildings]
-
A.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
B.
notableSetting
Indicates that a particular place or environment is especially significant or prominent as the context in which an entity is situated or occurs.
-
C.
notableFeat
Indicates that an entity is recognized for having achieved or performed a particularly significant or distinguished feat.
-
D.
notableStyleFeature
chosen
Indicates that an entity possesses a distinctive stylistic characteristic or design element that is especially noteworthy or defining.
-
E.
notableFeatureInStory
Indicates that a particular feature, element, or characteristic plays a significant or prominent role within a story.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e2c00648190ae2325e1ee58dcfd |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.