Triple
T7483918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALWEG |
E176830
|
entity |
| Predicate | monorailType |
P18634
|
FINISHED |
| Object | straddle‑beam |
—
|
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: straddle‑beam | Statement: [ALWEG, monorailType, straddle‑beam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monorailType Context triple: [ALWEG, monorailType, straddle‑beam]
-
A.
monorailOpeningDate
Indicates the calendar date on which a monorail system or line was first opened for public operation.
-
B.
thirdRailType
Indicates the specific design or configuration type of a third rail used in an electrified railway system.
-
C.
trainTypeUsed
Indicates that a specific type or category of train is employed or operated in a given context or service.
-
D.
railSystemType
chosen
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
E.
railServiceType
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
- 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f53923e4819081bf79ed962a971c |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:42 p.m.