Triple
T37486867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergeant Paul Jackson |
E931555
|
entity |
| Predicate | playableInMission |
P123406
|
FINISHED |
| Object | “Charlie Don’t Surf” |
—
|
NE NERFINISHED |
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: “Charlie Don’t Surf” | Statement: [Sergeant Paul Jackson, playableInMission, “Charlie Don’t Surf”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playableInMission Context triple: [Sergeant Paul Jackson, playableInMission, “Charlie Don’t Surf”]
-
A.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
B.
appearsInMission
chosen
Indicates that an entity participates in, is featured in, or occurs within a particular mission.
-
C.
containsMission
Indicates that one entity includes or encompasses a mission as part of its contents, scope, or responsibilities.
-
D.
enabledMission
Indicates that a mission has been activated or made available for execution or participation.
-
E.
hasMissionSystem
Indicates that an entity is equipped with or associated with a specific mission-related system or subsystem.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:17 p.m.