Triple
T19736472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moss Station |
E473995
|
entity |
| Predicate | hasZoneRole |
P79772
|
FINISHED |
| Object | regional transport hub |
—
|
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: regional transport hub | Statement: [Moss Station, hasZoneRole, regional transport hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZoneRole Context triple: [Moss Station, hasZoneRole, regional transport hub]
-
A.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
B.
hasZoneStatus
Indicates that a specified zone currently possesses a particular status or condition.
-
C.
zoningRole
chosen
Indicates the specific function, restriction, or regulatory status assigned to a property or area under zoning regulations.
-
D.
hasGlobalRole
Indicates that an entity holds a role or permission set that applies across an entire system or domain, rather than being limited to a specific scope or context.
-
E.
hasQuadrantRole
Indicates that an entity holds a specific functional or positional role within a defined quadrant of a larger structure or system.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6515ddea881909ea831b7bc16d934 |
completed | April 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.