Triple
T10242253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Jordan |
E243621
|
entity |
| Predicate | hasHereditaryAspect |
P92835
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Prince of Jordan, hasHereditaryAspect, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHereditaryAspect Context triple: [Prince of Jordan, hasHereditaryAspect, true]
-
A.
hereditaryInFamily
Indicates that a trait, condition, or characteristic is passed down through generations within the same family.
-
B.
hasHereditaryChief
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
-
C.
hereditaryAssociation
Indicates a relationship in which a trait, condition, or characteristic is passed from ancestors to descendants through genetic inheritance.
-
D.
hasTypeOfHeritage
Indicates that an entity is associated with a specific category or classification of heritage (such as cultural, natural, or historical heritage).
-
E.
hasHereditaryDesignation
chosen
Indicates that an entity possesses a title, status, or designation that is passed down through family lineage or inheritance.
- 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:25 a.m.