Triple
T9933500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Internet Registry |
E192700
|
entity |
| Predicate | canBeOperatedBy |
P52946
|
FINISHED |
| Object | large enterprise |
—
|
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: large enterprise | Statement: [Local Internet Registry, canBeOperatedBy, large enterprise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeOperatedBy Context triple: [Local Internet Registry, canBeOperatedBy, large enterprise]
-
A.
mayBeOperatedBy
chosen
Indicates that an entity has the potential or permission to be operated, controlled, or run by another entity.
-
B.
canOperateUnder
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.
-
C.
isOperatedIn
Indicates that an entity carries out its operations or activities within a specified location, region, or jurisdiction.
-
D.
canBeAdministeredBy
Indicates that one entity (such as a treatment, medication, or procedure) is capable of being given, applied, or carried out by another entity (such as a person, device, or system).
-
E.
canBeOpenedBy
Indicates that one entity has the ability or permission to open 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b89c808190a2e766025dd53bd5 |
completed | April 2, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:44 p.m.