Triple
T36898885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calculus of Constructions |
E911973
|
entity |
| Predicate | positionInLambdaCube |
P200929
|
FINISHED |
| Object | top corner |
—
|
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: top corner | Statement: [Calculus of Constructions, positionInLambdaCube, top corner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInLambdaCube Context triple: [Calculus of Constructions, positionInLambdaCube, top corner]
-
A.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
B.
positionInLent
Indicates the specific point or stage an event, day, or period occupies within the overall timeline of Lent.
-
C.
positionWithinOz
Indicates that one entity’s location is situated inside or within the spatial boundaries of another entity referred to as “Oz.”
-
D.
positionInCast
Indicates the specific role or placement an individual holds within the cast of a production, such as their billing order or credited position.
-
E.
positionWithinComplex
Indicates that one entity is located inside or forms a component part of a larger complex or compound structure.
- 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69ffb97ae1508190bf3addd6e2aac281 |
completed | May 9, 2026, 10:47 p.m. |
Created at: May 3, 2026, 4:13 p.m.