Triple
T714221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee on Codes of Conduct |
E14275
|
entity |
| Predicate | typeOfAdvice |
P6753
|
FINISHED |
| Object | nonbinding ethics advice |
—
|
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: nonbinding ethics advice | Statement: [Committee on Codes of Conduct, typeOfAdvice, nonbinding ethics advice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAdvice Context triple: [Committee on Codes of Conduct, typeOfAdvice, nonbinding ethics advice]
-
A.
guidanceType
chosen
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
B.
advises
Indicates that one entity provides guidance, recommendations, or counsel to another entity.
-
C.
typeOfRemedy
Indicates that one entity is a specific kind or category of remedy in relation to another entity.
-
D.
typeOfIncentive
Indicates the specific kind or category of incentive associated with an entity or action.
-
E.
appointmentOnAdviceOf
Indicates that an appointment or selection of someone to a position is made based on the recommendation, counsel, or formal advice of another person or authority.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a5738e04819082eac673b3b7c4c2 |
completed | March 1, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f38898819089d79bad4f4ff2d2 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.