Triple
T36593580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Working Group meeting |
E902733
|
entity |
| Predicate | mayBeHeldAs |
P191617
|
FINISHED |
| Object | in-person meeting |
—
|
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: in-person meeting | Statement: [Working Group meeting, mayBeHeldAs, in-person meeting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeHeldAs Context triple: [Working Group meeting, mayBeHeldAs, in-person meeting]
-
A.
canBeHeld
Indicates that an entity is capable of being physically grasped, supported, or carried by another entity.
-
B.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
C.
canBeHeldWith
Indicates that two entities are compatible or suitable to be held or used together at the same time.
-
D.
sometimesHeldBy
Indicates that one entity is occasionally or intermittently possessed, owned, or physically held by another entity, but not on a constant or permanent basis.
-
E.
isHeldAt
Indicates that an event, state, or condition occurs or is in effect at a specific time or temporal point.
- F. None of above. chosen
Provenance (4 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.