Triple
T1918513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Square |
E40072
|
entity |
| Predicate | hasNotableType |
P33147
|
FINISHED |
| Object | central public square |
—
|
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: central public square | Statement: [Green Square, hasNotableType, central public square]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableType Context triple: [Green Square, hasNotableType, central public square]
-
A.
hasNotableBridgeType
Indicates that an entity is associated with a specific, noteworthy type or design category of bridge.
-
B.
hasNotableSuccessorType
Indicates that an entity has a successor whose type or category is considered notably significant or distinguished in relation to it.
-
C.
hasNotableImplementationAt
Indicates that something has a significant or noteworthy implementation located at or associated with a particular place, context, or platform.
-
D.
hasNotableDescendant
Indicates that an entity has at least one descendant who is recognized as notable or significant in some context.
-
E.
hasNotableSegment
Indicates that an entity includes or contains a specific segment, part, or portion that is considered notable or significant in some way.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb211eda88190865de7a0522a453d |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb1b180e481908bbe893d6ba6208b |
completed | March 7, 2026, 5:03 a.m. |
Created at: March 4, 2026, 7:35 p.m.