Triple
T30341486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Fork Peachtree Creek Greenway |
E771764
|
entity |
| Predicate | hasConnectivityRole |
P203173
|
FINISHED |
| Object | trail network connector |
—
|
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: trail network connector | Statement: [South Fork Peachtree Creek Greenway, hasConnectivityRole, trail network connector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectivityRole Context triple: [South Fork Peachtree Creek Greenway, hasConnectivityRole, trail network connector]
-
A.
connectivityMode
Indicates how two or more entities are linked or able to communicate with each other, such as the type or method of connection used between them.
-
B.
connectsRole
Indicates a relationship in which one entity is linked to another by assigning or associating a specific role between them.
-
C.
hasPortRole
Indicates that an entity participates in a port with a specified functional or operational role.
-
D.
hasCircuitRole
Indicates that an entity participates in a circuit with a specific functional role or responsibility within that circuit.
-
E.
hasProtocolRole
Indicates that an entity participates in a protocol by fulfilling a specific role or function within that protocol.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a013632a3048190b05716d803f34716 |
completed | May 11, 2026, 1:51 a.m. |
| PD | Predicate disambiguation | batch_6a01309582e48190a05d47d96ffb7a46 |
completed | May 11, 2026, 1:27 a.m. |
| PDg | Predicate description generation | batch_6a013631f4d48190b1e79e8ff313d3d2 |
completed | May 11, 2026, 1:51 a.m. |
Created at: April 29, 2026, 7:55 p.m.