Triple
T18550718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 32 (Shenzhen Metro) |
E453366
|
entity |
| Predicate | networkMapRepresentation |
P31621
|
FINISHED |
| Object | Shenzhen Metro network map |
—
|
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: Shenzhen Metro network map | Statement: [Line 32 (Shenzhen Metro), networkMapRepresentation, Shenzhen Metro network map]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkMapRepresentation Context triple: [Line 32 (Shenzhen Metro), networkMapRepresentation, Shenzhen Metro network map]
-
A.
networkMap
Indicates a mapping relationship that shows how elements in a network are connected or arranged relative to one another.
-
B.
networkMapName
chosen
Indicates the designated name or label assigned to a particular network map within a system or context.
-
C.
networkMapGroup
Indicates a grouping relationship where multiple network elements are organized or associated together within a defined network map or topology group.
-
D.
networkModel
Indicates a relationship where an entity is represented or organized according to a specific network-based structure or framework.
-
E.
originalNetworkDepicted
Indicates that one entity visually represents or portrays the original network associated with 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53800c0fc819097782f1e81574598 |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:38 a.m.