Triple
T9319459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manhattan–Brooklyn |
E224207
|
entity |
| Predicate | hasModeOfConnection |
P62886
|
FINISHED |
| Object | road bridges |
—
|
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: road bridges | Statement: [Manhattan–Brooklyn, hasModeOfConnection, road bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModeOfConnection Context triple: [Manhattan–Brooklyn, hasModeOfConnection, road bridges]
-
A.
hasModeConnection
chosen
Indicates a relationship where one entity is linked to another through a specific mode, method, or type of connection.
-
B.
hasConnection
Indicates that there exists a link, association, or relationship between two entities.
-
C.
hasPlatformsConnectedBy
Indicates that two or more platforms are linked together by some connecting structure or mechanism.
-
D.
hasSurfaceConnection
Indicates that two entities are directly connected or in contact at their surfaces, allowing interaction or continuity between them.
-
E.
hasTeleconnectionsWith
Indicates a relationship where changes or variations in one system, region, or variable are statistically linked to corresponding changes in another, often distant, system, region, or variable.
- 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_69ca8426d48481909596360f7791c7dd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd358c7d348190a10fd8670d7756f5 |
completed | April 1, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:38 p.m.