Triple
T36230150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jura Federation |
E891217
|
entity |
| Predicate | positionOnOrganization |
P200564
|
FINISHED |
| Object | federalist |
—
|
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: federalist | Statement: [Jura Federation, positionOnOrganization, federalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnOrganization Context triple: [Jura Federation, positionOnOrganization, federalist]
-
A.
hasPositionInOrganization
Indicates that an entity holds a specific role, job, or position within a particular organization.
-
B.
locatedInOrganizationally
Indicates that one entity is organizationally situated within, or belongs to, another entity in terms of administrative or structural hierarchy.
-
C.
organizationalPlacement
Indicates how an entity is positioned or situated within an organization’s structure or hierarchy.
-
D.
positionInWork
Indicates the specific role, rank, or placement an entity holds within a larger work or structured composition.
-
E.
positionOnBusiness
Indicates the stance, role, or viewpoint an entity holds regarding a particular business, company, or commercial matter.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69ff965eef90819097499d1f0542378c |
completed | May 9, 2026, 8:17 p.m. |
Created at: May 3, 2026, 4:09 p.m.