Triple
T35074454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Classic Box |
E1011971
|
entity |
| Predicate | hasTypicalEntryLocation |
P28105
|
FINISHED |
| Object | centered front entry |
—
|
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: centered front entry | Statement: [Classic Box, hasTypicalEntryLocation, centered front entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalEntryLocation Context triple: [Classic Box, hasTypicalEntryLocation, centered front entry]
-
A.
hasEntryOn
Indicates that one entity contains or includes an entry, record, or listing about another entity.
-
B.
typicalEntryFile
Indicates that a given file is the standard or primary entry point typically used to start or access something (such as a program, project, or package).
-
C.
typicalEntryType
Indicates the usual or standard category or kind of entry associated with something.
-
D.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
E.
hasMainLocationType
chosen
Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff65987ff88190b09be64f7c0e1da9 |
completed | May 9, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69ff6525b0548190bef7a9f009e00bb8 |
completed | May 9, 2026, 4:47 p.m. |
Created at: May 3, 2026, 4:01 p.m.