Triple
T38369162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilot (Community) |
E892530
|
entity |
| Predicate | featuresStudyGroup |
P17143
|
FINISHED |
| Object | Spanish study group |
—
|
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: Spanish study group | Statement: [Pilot (Community), featuresStudyGroup, Spanish study group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresStudyGroup Context triple: [Pilot (Community), featuresStudyGroup, Spanish study group]
-
A.
featuresGroup
chosen
Indicates that an entity includes or is associated with a specific group as one of its features or components.
-
B.
studiesFeature
Indicates that an entity conducts research or examination on a particular feature or characteristic of something.
-
C.
featuresExperiment
Indicates that an entity is involved in, or is the subject of, a specific experimental setup, test, or trial.
-
D.
participantGroup
Indicates a relationship in which a set or group of entities jointly participate in a common event, activity, or interaction.
-
E.
featuresTopic
Indicates that something (such as a work, event, or item) prominently includes, focuses on, or is organized around a particular topic.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.