Triple
T6205149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirkiaceae |
E138726
|
entity |
| Predicate | familyNameEtymology |
P54694
|
FINISHED |
| Object | named after John Kirk |
—
|
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: named after John Kirk | Statement: [Kirkiaceae, familyNameEtymology, named after John Kirk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyNameEtymology Context triple: [Kirkiaceae, familyNameEtymology, named after John Kirk]
-
A.
nameEtymologyFor
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
-
B.
possibleNameEtymology
Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
-
C.
familyNameDerivedFrom
chosen
Indicates that one entity’s family name originates from, or is etymologically derived from, another entity.
-
D.
familyNameRefersTo
Indicates that a specified family name designates or refers to a particular person, group, or lineage.
-
E.
etymologicalLanguageFamily
Indicates that one entity is the language family from which the other entity is etymologically derived or historically originates.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0626d96ec8190816c00c44668177d |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.