Triple
T33579652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | idèle class group |
E860117
|
entity |
| Predicate | containsInformationAbout |
P86949
|
FINISHED |
| Object | ideal class 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: ideal class group | Statement: [idèle class group, containsInformationAbout, ideal class group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsInformationAbout Context triple: [idèle class group, containsInformationAbout, ideal class group]
-
A.
containsDataAbout
chosen
Indicates that one entity holds or includes information or records pertaining to another entity.
-
B.
providedInformationAbout
Indicates that one entity supplied or communicated information or details about another entity or topic to someone.
-
C.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
D.
controlsInformationAbout
Indicates that one entity has the authority or ability to manage, restrict, or direct access to information concerning another entity.
-
E.
providedInformationOn
Indicates that one entity supplied or communicated specific information or details to 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00315632a8819092290f455babd7ee |
completed | May 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_6a002f54a0dc81909b0e54c5e110e67c |
completed | May 10, 2026, 7:10 a.m. |
Created at: May 1, 2026, 1:40 a.m.