Triple
T30864145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Logan |
E786148
|
entity |
| Predicate | notablePlaceNamedInHonor |
P68977
|
FINISHED |
| Object | Logan Square |
E372526
|
NE 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: Logan Square | Statement: [James Logan, notablePlaceNamedInHonor, Logan Square]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlaceNamedInHonor Context triple: [James Logan, notablePlaceNamedInHonor, Logan Square]
-
A.
notablePlaceNamedAfter
chosen
Indicates that a notable place (such as a city, building, or landmark) is named in honor of or derived from the name of a particular entity.
-
B.
notableAsNamesakeOf
Indicates that one entity is recognized or distinguished specifically for being the namesake of another entity.
-
C.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
D.
notableLocationOn
Indicates that a particular location is especially significant or noteworthy in relation to a specified entity or context.
-
E.
notableUnitCommemorated
Indicates that a particular unit (such as a military or organizational unit) is specifically honored, remembered, or commemorated by something.
- F. None of above.
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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28e45664e88190beea7cf561b07f65 |
completed | June 10, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:47 p.m.