Triple
T21796589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helix City |
E538108
|
entity |
| Predicate | hasMobilityConcept |
P145683
|
FINISHED |
| Object | multi-level circulation networks |
—
|
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: multi-level circulation networks | Statement: [Helix City, hasMobilityConcept, multi-level circulation networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMobilityConcept Context triple: [Helix City, hasMobilityConcept, multi-level circulation networks]
-
A.
supportsMobilityType
Indicates that one entity provides compatibility with, or can function using, a specified type of mobility or movement mode.
-
B.
supportsMobilityFeature
Indicates that an entity provides or enables a mobility-related capability or feature for another entity.
-
C.
supportsMobilityBetween
Indicates that one entity enables, facilitates, or allows movement or travel between two or more other entities or locations.
-
D.
hasMob
Indicates that an entity possesses, controls, or is associated with a particular mob or group of mobile agents.
-
E.
mobilityComponent
Indicates that one entity functions as a mobility-related component or module that enables or affects the movement capabilities of another entity.
- F. None of above. chosen
Provenance (4 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0622502188190998638317f232334 |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6c3a2898881909748935cf92f898c |
completed | April 21, 2026, 12:24 a.m. |
Created at: April 16, 2026, 6:53 p.m.