Triple
T38587620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deeprun Tram entrance |
E932379
|
entity |
| Predicate | combatAllowed |
P151623
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Deeprun Tram entrance, combatAllowed, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatAllowed Context triple: [Deeprun Tram entrance, combatAllowed, no]
-
A.
attackFeasibility
Indicates the extent to which carrying out an attack is practically possible given current conditions, capabilities, and constraints.
-
B.
enablesWeaponlessCombat
Indicates that an entity provides the capability for another entity to engage in combat without using weapons.
-
C.
combatRules
chosen
Indicates the rules, mechanics, or conditions that govern how combat or fighting interactions are conducted between entities.
-
D.
attackTypesAllowed
Indicates which kinds or categories of attacks are permitted in a given context or interaction.
-
E.
hasAttackRestriction
Indicates that there is a limitation or condition placed on how, when, or whom an entity is allowed to attack.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.