Triple
T4331833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheshire cheese |
E96766
|
entity |
| Predicate | crumbStructure |
P55612
|
FINISHED |
| Object | open and crumbly |
—
|
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: open and crumbly | Statement: [Cheshire cheese, crumbStructure, open and crumbly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crumbStructure Context triple: [Cheshire cheese, crumbStructure, open and crumbly]
-
A.
routeStructure
Indicates the structural or organizational relationship between a route and its constituent segments, paths, or connections.
-
B.
rootStructure
Indicates that one entity serves as the primary or foundational structural element upon which another entity is based or organized.
-
C.
podStructure
Indicates a structural or compositional relationship in which one entity defines, organizes, or constitutes the internal structure of a pod-like grouping or unit.
-
D.
segmentStructure
Indicates that one entity represents a structural or organizational subdivision (a segment) within the overall structure of another entity.
-
E.
currentStructure
Indicates that an entity is the present or active structural configuration or organization associated with another entity.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3514dc588819086a4c6d585c1b5b1 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:13 p.m.