Triple
T4644938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hartelkering |
E101746
|
entity |
| Predicate | gateType |
P58877
|
FINISHED |
| Object | vertical lift gate |
—
|
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: vertical lift gate | Statement: [Hartelkering, gateType, vertical lift gate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gateType Context triple: [Hartelkering, gateType, vertical lift gate]
-
A.
doorType
Indicates the specific kind or category of door associated with an entity.
-
B.
gateWeight
Indicates the weight or importance assigned to a particular gate or transition within a process, model, or system.
-
C.
doorConfiguration
Indicates how a door is arranged or set up in relation to its frame, opening direction, and operational characteristics.
-
D.
gateOrientation
Indicates the directional alignment or facing direction of a gate relative to a reference frame or coordinate system.
-
E.
hasDoor
Indicates that one entity possesses or is equipped with a door that provides access to or through it.
- F. None of above. chosen
Provenance (4 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6632708c8190b627d99363ab062c |
completed | March 20, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69bd620fc5e081908325ac8e6a6384ab |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd663092cc81909308f89ee1a417e4 |
completed | March 20, 2026, 3:22 p.m. |
Created at: March 20, 2026, 1:14 p.m.