Triple
T32559414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bartertown |
E832181
|
entity |
| Predicate | combatArenaRule |
P151623
|
FINISHED |
| Object | Two men enter, one man leaves |
—
|
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: Two men enter, one man leaves | Statement: [Bartertown, combatArenaRule, Two men enter, one man leaves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatArenaRule Context triple: [Bartertown, combatArenaRule, Two men enter, one man leaves]
-
A.
combatRules
chosen
Indicates the rules, mechanics, or conditions that govern how combat or fighting interactions are conducted between entities.
-
B.
contestRule
Indicates that there is a rule or regulation governing how a contest is conducted or participated in.
-
C.
deathGameRule
Indicates a rule or condition within a deadly or lethal game that governs how participants must act or what consequences they face.
-
D.
competitionSquadRule
Indicates the rules or constraints governing how squads or teams must be composed or registered for a particular competition.
-
E.
reserveTeamRules
Indicates that there are specific rules or regulations governing the use, composition, or operation of a reserve team.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:03 a.m.