Triple
T22330154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Building No. 21 |
E552001
|
entity |
| Predicate | hasGridModule |
P12988
|
FINISHED |
| Object | Baťa 6.15 m construction module |
—
|
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: Baťa 6.15 m construction module | Statement: [Building No. 21, hasGridModule, Baťa 6.15 m construction module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGridModule Context triple: [Building No. 21, hasGridModule, Baťa 6.15 m construction module]
-
A.
hasServiceModule
Indicates that an entity is equipped with, or associated with, a specific service module that provides supporting or auxiliary functions.
-
B.
hasPanel
Indicates that one entity includes, is equipped with, or is associated with a panel as a component or feature.
-
C.
hasPlugin
Indicates that one entity includes, uses, or is extended by a plugin provided by another entity.
-
D.
hasModeIntegration
Indicates that one entity is integrated with, or supports integration of, a particular mode, method, or modality of operation.
-
E.
hasModuleConstruct
chosen
Indicates that an entity includes, defines, or is composed of a specific module as one of its structural or functional components.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1577a9c348190b8662142afa832be |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.