Triple
T28499044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monorail Line |
E721184
|
entity |
| Predicate | serviceClassificationWithin |
P18496
|
FINISHED |
| Object | Tama Monorail system |
—
|
NE NERFINISHED |
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: Tama Monorail system | Statement: [Monorail Line, serviceClassificationWithin, Tama Monorail system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceClassificationWithin Context triple: [Monorail Line, serviceClassificationWithin, Tama Monorail system]
-
A.
serviceClass
Indicates the classification or category of service associated with or provided by an entity in the relationship.
-
B.
publicServiceCategory
Indicates the classification or type of public service that an entity, activity, or offering belongs to.
-
C.
servicesType
Indicates the category or kind of services that one entity provides, uses, or is associated with in relation to another entity.
-
D.
serviceIn
chosen
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
E.
serviceIs
Indicates that one entity functions as a service of a specified type or category in relation to 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 28, 2026, 3:05 a.m.