Triple
T30087906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IC CE Series |
E764646
|
entity |
| Predicate | hasEntryConfiguration |
P13644
|
FINISHED |
| Object | high-floor design with steps |
—
|
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: high-floor design with steps | Statement: [IC CE Series, hasEntryConfiguration, high-floor design with steps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEntryConfiguration Context triple: [IC CE Series, hasEntryConfiguration, high-floor design with steps]
-
A.
hasConfiguration
chosen
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
B.
hasEntryOn
Indicates that one entity contains or includes an entry, record, or listing about another entity.
-
C.
hasEntryType
Indicates that something is associated with a specific category or type of entry within a system or dataset.
-
D.
hasEntryExample
Indicates that something includes or is associated with a specific example illustrating one of its entries.
-
E.
hasSubconfiguration
Indicates that an entity includes another entity as a subordinate or component configuration within its overall structure.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 7:04 p.m.