Triple
T37873556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violet Citadel |
E944662
|
entity |
| Predicate | notableLeaderPresent |
P304
|
FINISHED |
| Object | Rhonin |
E2234796
|
NE 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: Rhonin | Statement: [Violet Citadel, notableLeaderPresent, Rhonin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLeaderPresent Context triple: [Violet Citadel, notableLeaderPresent, Rhonin]
-
A.
notablePresence
Indicates that an entity has a significant or prominent presence in relation to another entity, context, or domain.
-
B.
hasNotableSpeaker
Indicates that an event, gathering, or occasion features a speaker who is distinguished or noteworthy in some significant way.
-
C.
hasNotableMember
chosen
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
-
D.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
E.
hasLeaderInNationalAssembly
Indicates that an entity has a designated leader who represents it within the national assembly.
- F. None of above.
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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a410428ba9881909d78eef0d96bbfde |
completed | June 28, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.