Triple
T20409892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toukan family |
E500560
|
entity |
| Predicate | knownForRoleIn |
P140036
|
FINISHED |
| Object | Jordanian politics |
—
|
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: Jordanian politics | Statement: [Toukan family, knownForRoleIn, Jordanian politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForRoleIn Context triple: [Toukan family, knownForRoleIn, Jordanian politics]
-
A.
famousRole
Indicates that an entity is best known for portraying or performing a particular role or character.
-
B.
knownForAct
Indicates that an entity is recognized or notable for performing a particular act or action.
-
C.
formerlyKnownFor
Indicates that an entity was previously recognized or notable for a particular role, attribute, or activity, but is no longer primarily associated with it.
-
D.
namedForKnownFor
Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
-
E.
refersToPersonKnownFor
Indicates that one entity makes reference to a person who is notable or recognized for some specific role, achievement, or characteristic.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a3e0c1c8190be39d7f09c839dfa |
completed | April 20, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:29 a.m.