Triple
T6281839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NADW |
E140798
|
entity |
| Predicate | ventilationTimescale |
P9981
|
FINISHED |
| Object | centuries |
—
|
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: centuries | Statement: [NADW, ventilationTimescale, centuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ventilationTimescale Context triple: [NADW, ventilationTimescale, centuries]
-
A.
ventilationFeature
Indicates that one entity has a structural or functional role related to providing, enabling, or affecting ventilation for another entity.
-
B.
timescale
chosen
Indicates the temporal scale or duration over which a process, relationship, or effect occurs or is evaluated.
-
C.
hasVentilationShafts
Indicates that one entity is equipped with or contains ventilation shafts that provide airflow or air passage.
-
D.
hasVentilationBuildings
Indicates that certain buildings are designated to provide ventilation for another structure, area, or system.
-
E.
timeScaleType
Indicates the type or category of temporal scaling applied to an event, process, or measurement (e.g., real-time, accelerated, aggregated).
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063dee62881908347283f16dcbe68 |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c05608a5608190b22a1fdc4060470d |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:26 p.m.