Triple
T11644812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | plane of immanence |
E276752
|
entity |
| Predicate | groundFor |
P32758
|
FINISHED |
| Object | Deleuzian concept of event |
—
|
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: Deleuzian concept of event | Statement: [plane of immanence, groundFor, Deleuzian concept of event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundFor Context triple: [plane of immanence, groundFor, Deleuzian concept of event]
-
A.
ground
Indicates that one entity is in contact with or supported by the ground or a ground-like surface.
-
B.
groundComponent
chosen
Indicates that one entity serves as a foundational or base part upon which another entity is built, attached, or functionally dependent.
-
C.
groundService
Indicates that one entity provides ground-based operational support or services to another entity, typically in a transportation or logistics context.
-
D.
coversGrounds
Indicates that one entity extends over, occupies, or lies across the surface area of another entity (typically land or grounds).
-
E.
globalGroundingStart
Indicates the point in time or event at which a globally shared or universally applicable grounding, context, or reference frame for subsequent information or actions begins.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cb4ca88190a9322f08416d3974 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.