Triple
T1348816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willson |
E28832
|
entity |
| Predicate | patronymicMeaning |
P24069
|
FINISHED |
| Object | son of Will |
—
|
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: son of Will | Statement: [Willson, patronymicMeaning, son of Will]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronymicMeaning Context triple: [Willson, patronymicMeaning, son of Will]
-
A.
patronymicName
Indicates that one entity’s name is derived from or based on the given name of a parent or ancestor, typically the father.
-
B.
isMatronymicOf
Indicates that one entity is a name or designation derived from the mother of another entity, typically used as that entity’s family or identifying name.
-
C.
hasGivenNameMeaning
chosen
Indicates that a given name carries a particular meaning or semantic interpretation.
-
D.
fatherName
Indicates that one entity is the name of the father of another entity.
-
E.
reasonForEpithet
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c268745481908be649526c18e558 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.