Triple
T25625513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orville Wright Middle School |
E642418
|
entity |
| Predicate | hasNamesakeFamilyName |
P168034
|
FINISHED |
| Object | Wright |
—
|
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: Wright | Statement: [Orville Wright Middle School, hasNamesakeFamilyName, Wright]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamesakeFamilyName Context triple: [Orville Wright Middle School, hasNamesakeFamilyName, Wright]
-
A.
namesakeFamily
Indicates that one entity is a family or familial group that shares the same name as, or is named after, another entity.
-
B.
hasHonorificNamesake
Indicates that an entity is named in honor of another entity, serving as a namesake that recognizes or commemorates the other.
-
C.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
D.
hasAncestralFamilyNameMeaning
Indicates that an entity’s ancestral family name carries a specific meaning or significance.
-
E.
refersToNotableFamily
Indicates that an entity is associated with, or makes reference to, a specific well-known or historically significant family.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 21, 2026, 5:14 p.m.