Triple
T6487077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wuhan Metro Line 12 |
E146538
|
entity |
| Predicate | plannedServiceArea |
P60867
|
FINISHED |
| Object | central urban area of Wuhan |
—
|
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: central urban area of Wuhan | Statement: [Wuhan Metro Line 12, plannedServiceArea, central urban area of Wuhan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedServiceArea Context triple: [Wuhan Metro Line 12, plannedServiceArea, central urban area of Wuhan]
-
A.
plannedArea
chosen
Indicates that an area is designated or intended for a specific planned use or development.
-
B.
areaServed
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
C.
areaServedType
Indicates the type or category of area that is served by an entity or service.
-
D.
plannedService
Indicates that a service is scheduled or intended to be provided, but has not yet occurred.
-
E.
hasServiceAreas
Indicates that an entity provides services within, or is operational across, specific geographic or functional areas.
- 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_69c0090158c08190af0df9a2348d2d52 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a96a4048190a28dee5fd9258486 |
completed | March 22, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:52 p.m.