Triple
T16959839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tromp family |
E411397
|
entity |
| Predicate | hasFamilyTradition |
P19423
|
FINISHED |
| Object | naval command |
—
|
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: naval command | Statement: [Tromp family, hasFamilyTradition, naval command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyTradition Context triple: [Tromp family, hasFamilyTradition, naval command]
-
A.
hasTraditionIn
chosen
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
B.
isTraditionOf
Indicates that something is a customary practice, belief, or ritual associated with or belonging to a particular group, culture, or context.
-
C.
hasFamilyTrait
Indicates that a particular trait or characteristic is shared among members of the same family or lineage.
-
D.
hasFamilyBackgroundIn
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
E.
hasChildrenInTradition
Indicates that an entity has one or more children specifically within the context of a particular tradition, lineage, or customary framework.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01f9ba881908dc8820b92869a63 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.