Triple
T10513325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunant family |
E247970
|
entity |
| Predicate | hasNotableLineageFor |
P94318
|
FINISHED |
| Object | humanitarian activities |
—
|
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: humanitarian activities | Statement: [Dunant family, hasNotableLineageFor, humanitarian activities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLineageFor Context triple: [Dunant family, hasNotableLineageFor, humanitarian activities]
-
A.
hasNotableLineage
Indicates that an entity descends from, or is associated with, a distinguished or historically significant family, ancestry, or heritage.
-
B.
hasLineageDocumentedIn
Indicates that the lineage or ancestry of an entity is recorded or evidenced in a specified document or source.
-
C.
hasLineageStructure
Indicates that an entity participates in or exhibits a hierarchical ancestry or lineage-based structural relationship to other entities.
-
D.
hasLineageMember
Indicates that one entity is a member or descendant within the lineage or ancestral line of another entity.
-
E.
hasLineageRole
Indicates a relationship where an entity holds a specific role or function within a lineage, ancestry, or genealogical chain.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509ca214481909b3ed9265e7a6704 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:27 p.m.