Triple
T7884739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ekistics |
E183073
|
entity |
| Predicate | appliesToScale |
P1129
|
FINISHED |
| Object | building |
—
|
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: building | Statement: [ekistics, appliesToScale, building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToScale Context triple: [ekistics, appliesToScale, building]
-
A.
scalesWith
Indicates that a change in one quantity is systematically associated with a proportional or otherwise dependent change in another quantity.
-
B.
hasScale
Indicates that one entity possesses or is characterized by a scale or graduated measurement system related to another entity.
-
C.
appliesTo
chosen
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
D.
associatedScale
Indicates that one entity is linked or connected to a particular scale used to measure, classify, or evaluate it.
-
E.
hasScales
Indicates that an entity possesses scales as a surface covering or body feature.
- 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_69ca828af6e48190a06ee7010d8f0e64 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39d62a148190bed4e0d199aa427b |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:59 p.m.