Triple
T32068136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip Sherman |
E818938
|
entity |
| Predicate | targetOfEscapePlanBy |
P166034
|
FINISHED |
| Object | tank gang |
—
|
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: tank gang | Statement: [Philip Sherman, targetOfEscapePlanBy, tank gang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetOfEscapePlanBy Context triple: [Philip Sherman, targetOfEscapePlanBy, tank gang]
-
A.
escapePlanDevisedBy
chosen
Indicates that an escape plan was created, formulated, or arranged by a particular entity.
-
B.
escapePlanRole
Indicates that an entity participates in an escape plan with a specific role or function within that plan.
-
C.
plansToFlee
Indicates an entity’s intention or decision to escape or leave a place or situation, typically in a secretive or urgent manner.
-
D.
escapeLocation
Indicates that an entity moves away from or leaves a location to avoid danger, capture, or an undesirable situation.
-
E.
targetOfThreat
Indicates that one entity is the recipient or intended victim of a threat made by another entity.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 1, 2026, 12:22 a.m.