Triple
T25617803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | thing (Germanic assembly) |
E642204
|
entity |
| Predicate | hasDecisionMethod |
P146302
|
FINISHED |
| Object | consensus |
—
|
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: consensus | Statement: [thing (Germanic assembly), hasDecisionMethod, consensus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDecisionMethod Context triple: [thing (Germanic assembly), hasDecisionMethod, consensus]
-
A.
hasDecisionPoint
Indicates that there is a specific moment or juncture at which a choice between alternative options or paths must be made.
-
B.
hasDecisionMaker
Indicates that one entity serves as the decision-making authority or agent for another entity.
-
C.
hasDecisionForm
Indicates that an entity is associated with, or represented by, a particular decision document or formal decision record.
-
D.
hasOutcomeSelectionMethod
chosen
Indicates the method or criteria used to select or determine the outcome of a process, event, or decision.
-
E.
decidedWith
Indicates that an entity made a decision jointly or in agreement with another entity.
- F. None of above.
Provenance (3 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 21, 2026, 5:01 p.m.