Triple
T22234751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oʻahu freeway network |
E549561
|
entity |
| Predicate | primaryModeSupported |
P110722
|
FINISHED |
| Object | motor vehicle traffic |
—
|
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: motor vehicle traffic | Statement: [Oʻahu freeway network, primaryModeSupported, motor vehicle traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryModeSupported Context triple: [Oʻahu freeway network, primaryModeSupported, motor vehicle traffic]
-
A.
hasPrimaryModeSupported
chosen
Indicates that an entity supports a particular mode as its main or default mode of operation.
-
B.
supportedMode
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
-
C.
availableInMode
Indicates that something can be used, accessed, or functions within a specified mode or operational setting.
-
D.
primaryModes
Indicates the main methods, forms, or channels through which something typically operates, is expressed, or is carried out.
-
E.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12bf61504819093e70bee4c575d1c |
completed | April 28, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:38 p.m.