Triple
T28766839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justin Herman |
E726297
|
entity |
| Predicate | hasNameInCommon |
P20785
|
FINISHED |
| Object | Justin Herman Plaza |
—
|
NE NERFINISHED |
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: Justin Herman Plaza | Statement: [Justin Herman, hasNameInCommon, Justin Herman Plaza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInCommon Context triple: [Justin Herman, hasNameInCommon, Justin Herman Plaza]
-
A.
nameIsCommonIn
Indicates that a given name is frequently used or widely occurring within a specified group, region, or context.
-
B.
hasLastNameInCommonWith
Indicates that two entities share the same last name.
-
C.
sharesGivenNameWith
chosen
Indicates that two entities have the same given (first) name.
-
D.
sharesSurnameWithMany
Indicates that an entity has the same surname as a large number of other entities.
-
E.
hasGivenNameCounterpart
Indicates that one entity is the given-name (first-name) counterpart or variant of another entity, typically linking related personal names.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 28, 2026, 6:14 a.m.