Triple
T32130865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Welcome to the Jungle |
E820637
|
entity |
| Predicate | RobHuebelRoleType |
P5518
|
FINISHED |
| Object | office employee |
—
|
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: office employee | Statement: [Welcome to the Jungle, RobHuebelRoleType, office employee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RobHuebelRoleType Context triple: [Welcome to the Jungle, RobHuebelRoleType, office employee]
-
A.
typeOfRole
chosen
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
B.
RobMorrowRole
Indicates that a person has played a specific role in a work featuring Rob Morrow.
-
C.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
D.
eraRole
Indicates the specific role, function, or capacity an entity has within a particular historical or temporal era.
-
E.
roleOn
Indicates that an entity holds or performs a specific role or function within another entity, context, or activity.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b97009cc819093326ec5c6a56083 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:29 a.m.