Triple
T714039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Science of Logic |
E14271
|
entity |
| Predicate | positionInOeuvre |
P5188
|
FINISHED |
| Object | major systematic work |
—
|
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: major systematic work | Statement: [Science of Logic, positionInOeuvre, major systematic work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInOeuvre Context triple: [Science of Logic, positionInOeuvre, major systematic work]
-
A.
positionInShow
Indicates the specific order or placement an entity occupies within a show, series, or sequence of performances or episodes.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
positionInWork
chosen
Indicates the specific role, rank, or placement an entity holds within a larger work or structured composition.
-
D.
positionSpecific
Indicates that something applies only at, or is defined with respect to, a particular position or location within a larger structure or sequence.
-
E.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a77fcc6881908a025bb21e44ad56 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f221b081909fbaa689fb20eb3e |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.