Triple
T27771149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sister's Meal Festival |
E701748
|
entity |
| Predicate | hiddenItemMeaning |
P124062
|
FINISHED |
| Object | chili indicates passionate love |
—
|
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: chili indicates passionate love | Statement: [Sister's Meal Festival, hiddenItemMeaning, chili indicates passionate love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hiddenItemMeaning Context triple: [Sister's Meal Festival, hiddenItemMeaning, chili indicates passionate love]
-
A.
hiddenIn
Indicates that one entity is concealed within, behind, or inside another entity so that it is not readily visible or apparent.
-
B.
objectMeaning
chosen
Indicates that one entity represents, expresses, or conveys the meaning or semantic content of another entity.
-
C.
logicalMeaning
Indicates that one entity expresses, encodes, or conveys the logical content, implication, or formal meaning of another.
-
D.
revealedSecretOf
Indicates that one entity has disclosed or exposed confidential or previously unknown information belonging to another entity.
-
E.
hiddenAt
Indicates that one entity is concealed or stored at a specific location or within 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63796dd688190a72de4e61faaac9b |
completed | May 2, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:35 p.m.