Triple
T27835548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molino |
E703215
|
entity |
| Predicate | isOccupationalSurnameRelatedTo |
P28498
|
FINISHED |
| Object | miller |
—
|
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: miller | Statement: [Molino, isOccupationalSurnameRelatedTo, miller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOccupationalSurnameRelatedTo Context triple: [Molino, isOccupationalSurnameRelatedTo, miller]
-
A.
isOccupationalSurname
chosen
Indicates that a surname originates from or is derived from a person’s occupation or trade.
-
B.
hasOccupationRelative
Indicates that one entity has another entity as a relative who holds a particular occupation or job.
-
C.
associatedSurname
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
D.
isRelatedName
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
-
E.
isSurname
Indicates that one entity is the family name (last name) of another 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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:59 p.m.