Triple
T3300735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R11 |
E69323
|
entity |
| Predicate | appliesToStructureType |
P841
|
FINISHED |
| Object | underground station complex |
—
|
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: underground station complex | Statement: [R11, appliesToStructureType, underground station complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToStructureType Context triple: [R11, appliesToStructureType, underground station complex]
-
A.
appliesToPropertyType
Indicates that something (such as a rule, constraint, or operation) is relevant to or valid for a specific type of property.
-
B.
hasStructureType
chosen
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
C.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
D.
appliesToProductType
Indicates that something (such as a rule, offer, or condition) is relevant or applicable specifically to a certain type or category of product.
-
E.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a7d224819080d9a638e08bb8a8 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.