Triple
T19703336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friends of O'Reilly Camp |
E473149
|
entity |
| Predicate | hasSessionFormat |
P1266
|
FINISHED |
| Object | self-organized sessions |
—
|
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: self-organized sessions | Statement: [Friends of O'Reilly Camp, hasSessionFormat, self-organized sessions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSessionFormat Context triple: [Friends of O'Reilly Camp, hasSessionFormat, self-organized sessions]
-
A.
hasSession
chosen
Indicates that an entity is associated with, participates in, or contains a particular session instance.
-
B.
hasFormatCurrent
Indicates that an entity is available or expressed in the currently used or most up-to-date format.
-
C.
hasConfigurationFormat
Indicates that an entity uses or is associated with a specific configuration format for its settings or parameters.
-
D.
hasWorkingFormat
Indicates that one entity possesses or is associated with a functional or operational format of another entity.
-
E.
hasMatchFormat
Indicates that something (such as a game, event, or competition) is conducted according to a specified match format or structure.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b8707081908fbf96c989d2d52d |
completed | April 20, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.