Triple
T33074539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gherardini |
E846321
|
entity |
| Predicate | familyNameDerivedFromLocation |
P54694
|
FINISHED |
| Object | Florence |
—
|
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: Florence | Statement: [Gherardini, familyNameDerivedFromLocation, Florence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyNameDerivedFromLocation Context triple: [Gherardini, familyNameDerivedFromLocation, Florence]
-
A.
familyNameDerivedFrom
chosen
Indicates that one entity’s family name originates from, or is etymologically derived from, another entity.
-
B.
surnameLikelyOriginRegion
Indicates the geographic region from which a person’s surname is most likely to have originated.
-
C.
familyNamePattern
Indicates that there is a specific structural or formatting pattern that a family name (surname) follows.
-
D.
familyName
Indicates that one entity is the family (last) name associated with another entity (typically a person).
-
E.
familyNamePart
Indicates that one string is a component or segment of a person's full family name.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 1, 2026, 1:25 a.m.