Triple
T28005811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF participants |
E707270
|
entity |
| Predicate | mayParticipate |
P88995
|
FINISHED |
| Object | remotely |
—
|
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: remotely | Statement: [IETF participants, mayParticipate, remotely]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayParticipate Context triple: [IETF participants, mayParticipate, remotely]
-
A.
mayEngageIn
Indicates that one entity is permitted or authorized to participate in or perform a particular activity or interaction with another entity.
-
B.
mayAttend
chosen
Indicates that an entity is permitted or eligible to be present at or participate in a particular event, activity, or gathering.
-
C.
mayApply
Indicates that an entity is permitted or eligible to submit or use something (such as a rule, action, or resource) under certain conditions.
-
D.
mayTake
Indicates that an entity is permitted or allowed to take, enroll in, or participate in another entity (such as a course, resource, or opportunity).
-
E.
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.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63bd61d608190b782e6e692cd68c5 |
completed | May 2, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8 p.m.