Triple
T35010155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raven Rock |
E1009920
|
entity |
| Predicate | primaryLeaderPresent |
P203865
|
FINISHED |
| Object | President John Henry Eden |
E1009917
|
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: President John Henry Eden | Statement: [Raven Rock, primaryLeaderPresent, President John Henry Eden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLeaderPresent Context triple: [Raven Rock, primaryLeaderPresent, President John Henry Eden]
-
A.
centralLeader
Indicates that an entity serves as the primary or most important leader within a group, organization, or system.
-
B.
hasPrimaryRoleOfLeader
chosen
Indicates that an entity holds the main or most authoritative leadership role within a given context or group.
-
C.
initialLeader
Indicates that an entity serves as the first or original leader of another entity, typically at the start of its existence or a defined period.
-
D.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
E.
establishedUnderLeader
Indicates that an entity was founded, created, or formally established during the tenure or authority of a specific leader.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37c6295f908190a88596e03fb374ba |
completed | June 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.