Triple
T35345560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSI 3* |
E1020728
|
entity |
| Predicate | sanctioningRequirement |
P28477
|
FINISHED |
| Object | must be approved by FEI |
—
|
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: must be approved by FEI | Statement: [CSI 3*, sanctioningRequirement, must be approved by FEI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanctioningRequirement Context triple: [CSI 3*, sanctioningRequirement, must be approved by FEI]
-
A.
requiresSanctioningBody
chosen
Indicates that an action, event, or decision must be approved or authorized by a designated sanctioning authority or governing body.
-
B.
sanctionedUnder
Indicates that an action, decision, or status is authorized, approved, or imposed in accordance with a specific rule, law, policy, or regulatory framework.
-
C.
policyRequirement
Indicates that one entity specifies a rule, condition, or obligation that another entity must satisfy according to a policy.
-
D.
sanctioningRules
Indicates the rules or conditions under which sanctions or penalties are imposed in response to certain actions or behaviors.
-
E.
establishedRequirement
Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
- 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.