Triple
T35118735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poor Fellows |
E1014110
|
entity |
| Predicate | armorPolicy |
P73638
|
FINISHED |
| Object | simple armor or no armor |
—
|
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: simple armor or no armor | Statement: [Poor Fellows, armorPolicy, simple armor or no armor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armorPolicy Context triple: [Poor Fellows, armorPolicy, simple armor or no armor]
-
A.
eraPolicy
Indicates that a specific policy was in effect during a particular historical or temporal era.
-
B.
protectionPolicy
chosen
Indicates that one entity establishes or enforces rules or measures to safeguard another entity from harm, loss, or risk.
-
C.
admissionPolicy
Indicates the rules or criteria governing whether and how entities are allowed to be admitted or granted access.
-
D.
appliesPolicyOn
Indicates that one entity enforces, executes, or brings into effect a specific policy on another entity or context.
-
E.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.