Triple
T6842019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Menu |
E157795
|
entity |
| Predicate | codenameScheme |
P65002
|
FINISHED |
| Object | meal-related code names |
—
|
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: meal-related code names | Statement: [Operation Menu, codenameScheme, meal-related code names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codenameScheme Context triple: [Operation Menu, codenameScheme, meal-related code names]
-
A.
codenameUser
Indicates that a user is assigned or associated with a particular codename.
-
B.
endUseAsCodename
Indicates that an entity stops being used as a codename for another entity or concept.
-
C.
usesCodeName
Indicates that one entity refers to another entity by a code name or alias instead of its real or full designation.
-
D.
codeNameCategory
chosen
Indicates that an entity’s code name belongs to or is classified under a particular category of code names.
-
E.
relatedCodename
Indicates that one entity has an associated or connected codename that is contextually related to it.
- 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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6b5f7648190ad8561caeb678932 |
completed | March 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:19 p.m.