Triple
T22577981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 6th Sense |
E544466
|
entity |
| Predicate | typicalRoleInProjects |
P18942
|
FINISHED |
| Object | producer |
—
|
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: producer | Statement: [6th Sense, typicalRoleInProjects, producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRoleInProjects Context triple: [6th Sense, typicalRoleInProjects, producer]
-
A.
typicalRole
chosen
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
B.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
C.
roleInProjectLifecycle
Indicates the specific function or responsibility an entity has at a particular stage of a project's lifecycle.
-
D.
typicalAdditionalRole
Indicates that an entity commonly or characteristically holds an extra role or function in addition to its primary one.
-
E.
roleInExperience
Indicates the specific function, position, or part an entity plays within a particular experience or event.
- 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f15feee27c8190b31c923e1f00a363 |
completed | April 29, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:53 p.m.