Triple
T25261982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pie |
E633327
|
entity |
| Predicate | commonFilling |
P13702
|
FINISHED |
| Object | Apple |
—
|
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: Apple | Statement: [Pie, commonFilling, Apple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonFilling Context triple: [Pie, commonFilling, Apple]
-
A.
isTypicallyFilledWith
chosen
Indicates that one entity is commonly or usually occupied, loaded, or contained by another entity.
-
B.
traditionalFilling
Indicates that something is filled using a customary or historically established type of filling associated with a particular practice, item, or cuisine.
-
C.
wasInfilling
Indicates that one entity was in the process of filling or occupying a space, gap, or area within another entity or context.
-
D.
fillsInteriorWith
Indicates that one entity occupies and completes the inside space or volume of another entity by putting something into its interior.
-
E.
mayBeFilledBy
Indicates that one entity has the potential or permission to be occupied, completed, or satisfied by another entity.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 1:14 p.m.