Triple
T32644716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Big Dog |
E834567
|
entity |
| Predicate | entranceTrait |
P174764
|
FINISHED |
| Object | crowd through-the-audience entrance (early singles run) |
—
|
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: crowd through-the-audience entrance (early singles run) | Statement: [The Big Dog, entranceTrait, crowd through-the-audience entrance (early singles run)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entranceTrait Context triple: [The Big Dog, entranceTrait, crowd through-the-audience entrance (early singles run)]
-
A.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
B.
entranceDesigner
Indicates that an entity is responsible for designing the entrance of a building, structure, or space.
-
C.
entranceVisibility
Indicates how easily or clearly an entrance can be seen or recognized from a given viewpoint or approach.
-
D.
entranceShape
Indicates the geometric form or outline that characterizes an entrance.
-
E.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
- F. None of above. chosen
Provenance (4 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7e32ec08190b74856937c4a9fc3 |
completed | May 3, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:07 a.m.