Triple
T5618893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wuhan Metro Line 19 |
E147548
|
entity |
| Predicate | expectedFunction |
P13995
|
FINISHED |
| Object | mass transit for commuters |
—
|
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: mass transit for commuters | Statement: [Wuhan Metro Line 19, expectedFunction, mass transit for commuters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedFunction Context triple: [Wuhan Metro Line 19, expectedFunction, mass transit for commuters]
-
A.
possibleFunction
Indicates that an entity may serve, or is capable of serving, a particular function or role, without asserting that it actually does so.
-
B.
intendedFunction
chosen
Indicates that something is designed or purposed to perform a particular role, use, or function.
-
C.
usesFunction
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
-
D.
endedFunctionallyWith
Indicates that a process, event, or relationship has effectively concluded in practice, even if it has not been formally or officially terminated.
-
E.
assignedFunction
Indicates that a specific role, duty, or function has been formally allocated to an 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_69c00905d4588190bd967842bbcf2219 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c021dd5d0081909d18d16596fac507 |
completed | March 22, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.