Triple
T2190820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Credo |
E49855
|
entity |
| Predicate | statesResponsibilityTo |
P34
|
FINISHED |
| Object | customers |
—
|
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: customers | Statement: [Our Credo, statesResponsibilityTo, customers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statesResponsibilityTo Context triple: [Our Credo, statesResponsibilityTo, customers]
-
A.
reservesAuthorityToStatesOver
Indicates that a higher-level authority explicitly retains or assigns decision-making power on a given matter to individual states rather than exercising it centrally.
-
B.
states
chosen
Indicates that an entity formally declares, expresses, or asserts a fact, opinion, or condition about another entity or situation.
-
C.
memberStatesContribute
Indicates that member states provide resources, support, or participation toward a shared goal, activity, or entity.
-
D.
statesGoal
Indicates that one entity explicitly expresses or declares a goal or intended outcome related to another entity or situation.
-
E.
responsibleFor
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.