Triple
T2933837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl |
E79216
|
entity |
| Predicate | associatedWithRoyalty |
P44025
|
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: [Karl, associatedWithRoyalty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRoyalty Context triple: [Karl, associatedWithRoyalty, true]
-
A.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
B.
associatedWithRule
Indicates that an entity is linked or connected to a specific rule, such as being governed, constrained, or defined by that rule.
-
C.
associatedWithRank
Indicates a relationship where an entity is linked to a specific rank, level, or hierarchical position.
-
D.
relatedCommission
Indicates that one commission is connected or associated with another commission in a relevant contextual or functional way.
-
E.
associatedWithExchange
Indicates a relationship in which an entity is linked or connected to a particular exchange or trading platform.
- 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad983b65f881909b8b7d3dc5c224fd |
completed | March 8, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:56 p.m.