Triple
T4111367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humboldt family |
E88579
|
entity |
| Predicate | familyNameDerivedFrom |
P54694
|
FINISHED |
| Object | place name Humboldt |
—
|
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: place name Humboldt | Statement: [Humboldt family, familyNameDerivedFrom, place name Humboldt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyNameDerivedFrom Context triple: [Humboldt family, familyNameDerivedFrom, place name Humboldt]
-
A.
familyName
Indicates that one entity is the family (last) name associated with another entity (typically a person).
-
B.
familyNameCategory
Indicates that an entity is associated with a particular classification or grouping based on its family name.
-
C.
dynasticNameDerivedFrom
Indicates that a dynastic name is derived from, or based on, another name, title, or source.
-
D.
associatedSurname
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
E.
patronymicName
Indicates that one entity’s name is derived from or based on the given name of a parent or ancestor, typically the father.
- 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_69aed9484fb881909146f4c772ad277c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af03d5cce88190ad53bc6cfe10b21e |
completed | March 9, 2026, 5:31 p.m. |
Created at: March 9, 2026, 3:41 p.m.