Triple
T4190655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count (continental Europe) |
E89025
|
entity |
| Predicate | oftenHereditaryIn |
P31750
|
FINISHED |
| Object | noble families |
—
|
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: noble families | Statement: [Count (continental Europe), oftenHereditaryIn, noble families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenHereditaryIn Context triple: [Count (continental Europe), oftenHereditaryIn, noble families]
-
A.
nonHereditary
Indicates that a trait, condition, or status is not passed down genetically from parents to offspring.
-
B.
hasHereditaryChief
chosen
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
-
C.
recognizedSexLinkedTraits
Indicates that an entity has identified and acknowledged traits whose inheritance is linked to sex chromosomes.
-
D.
geneticInfluence
Indicates that one entity affects or contributes to the genetic traits, characteristics, or heredity of another entity.
-
E.
hasFamilialForm
Indicates that one entity has a version, variant, or form that is specifically used in familial or family-related contexts in relation to another entity.
- 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:46 p.m.