Triple
T25926905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manning Award |
E653329
|
entity |
| Predicate | namesakeFamily |
P160303
|
FINISHED |
| Object | Manning family |
—
|
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: Manning family | Statement: [Manning Award, namesakeFamily, Manning family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namesakeFamily Context triple: [Manning Award, namesakeFamily, Manning family]
-
A.
namesakeDescription
Indicates that the object provides a descriptive explanation of why or how the subject is considered a namesake of something or someone.
-
B.
namesakeFullName
Indicates that one entity’s full name is used as the namesake or source of the name for another entity.
-
C.
namesakeNationality
Indicates that one entity has the same nationality as the person or entity after whom it is named.
-
D.
namesakeType
Indicates the specific kind or category of namesake relationship that exists between two entities (for example, one being named after the other as a person, place, event, or object).
-
E.
familyNameIn
Indicates that an entity has a specified family name (surname) in a particular language or cultural context.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6041473b08190a9b421b06f24b615 |
completed | May 2, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 22, 2026, 8:35 a.m.