Triple
T10054371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PTC |
E208824
|
entity |
| Predicate | mayOperateUnder |
P15906
|
FINISHED |
| Object | international organization |
—
|
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: international organization | Statement: [PTC, mayOperateUnder, international organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayOperateUnder Context triple: [PTC, mayOperateUnder, international organization]
-
A.
canOperateUnder
chosen
Indicates that one entity is permitted, able, or qualified to function, perform, or remain active within the conditions, authority, or environment defined by another entity.
-
B.
mayBeOperatedBy
Indicates that an entity has the potential or permission to be operated, controlled, or run by another entity.
-
C.
mayConduct
Indicates that one entity is permitted or authorized to carry out, perform, or execute a particular action, process, or operation on or with another entity.
-
D.
mayActThrough
Indicates that an entity can exert influence, perform an action, or have an effect by means of another entity, mechanism, or intermediary.
-
E.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfab39408190ac728fe156eed658 |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:57 p.m.