Triple
T17681594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extended Essay |
E440782
|
entity |
| Predicate | topicMustBe |
P128552
|
FINISHED |
| Object | aligned with one IB Diploma subject |
—
|
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: aligned with one IB Diploma subject | Statement: [Extended Essay, topicMustBe, aligned with one IB Diploma subject]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topicMustBe Context triple: [Extended Essay, topicMustBe, aligned with one IB Diploma subject]
-
A.
primaryTopicOf
Indicates that a given subject is the main or central topic described by another resource (such as a document, page, or record).
-
B.
followsTopic
Indicates that one entity subscribes to or tracks updates, content, or activity related to a particular topic associated with another entity.
-
C.
subjectCanBe
Indicates that the subject has the potential or capability to assume, become, or be classified as the specified object or state.
-
D.
subjectMVP
Indicates that the subject is considered the most valuable player (MVP) in a given context or event.
-
E.
topicOfDialogue
Indicates that a particular subject or theme is the main focus of a dialogue or conversation between entities.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e470445b3881908bb0930b986089f7 |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:01 a.m.