Triple
T3584222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Square Park |
E75871
|
entity |
| Predicate | hasPathLayout |
P10827
|
FINISHED |
| Object | formal paths around central fountain |
—
|
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: formal paths around central fountain | Statement: [Washington Square Park, hasPathLayout, formal paths around central fountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPathLayout Context triple: [Washington Square Park, hasPathLayout, formal paths around central fountain]
-
A.
hasLayout
chosen
Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of another entity.
-
B.
hasLayOrder
Indicates that one entity has issued, received, or is subject to a formal lay order associated with another entity.
-
C.
hasTopology
Indicates that one entity possesses, exhibits, or is characterized by a particular structural or spatial configuration defined by the other entity.
-
D.
driveLayoutSupported
Indicates that a particular drive layout or configuration is compatible with and can be correctly handled by a given system or component.
-
E.
hasPathway
Indicates that there exists a route, channel, or sequence of steps through which one entity leads, connects, or gives access to another.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc10f9b508190bde4a4e4711dd452 |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.