Triple
T9617102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linguini |
E232244
|
entity |
| Predicate | initialRoleAtGusteaus |
P80578
|
FINISHED |
| Object | garbage boy |
—
|
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: garbage boy | Statement: [Linguini, initialRoleAtGusteaus, garbage boy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialRoleAtGusteaus Context triple: [Linguini, initialRoleAtGusteaus, garbage boy]
-
A.
settingRole
Indicates that an entity functions in a particular contextual or environmental role within a given setting or situation.
-
B.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
C.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
-
D.
earlyRole
chosen
Indicates that an entity held a particular role or position during an early or initial stage of its involvement or development.
-
E.
questRole
Indicates the specific function or part an entity plays within a quest or mission.
- 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_69ca84867bb88190b4b57dd5a56d5691 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9aaf3a088190a00a7750c25b6c42 |
completed | April 1, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:09 p.m.