Triple
T29059950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forces of James Scott, 1st Duke of Monmouth |
E735499
|
entity |
| Predicate | equipmentQuality |
P71865
|
FINISHED |
| Object | largely ill-equipped |
—
|
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: largely ill-equipped | Statement: [Forces of James Scott, 1st Duke of Monmouth, equipmentQuality, largely ill-equipped]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equipmentQuality Context triple: [Forces of James Scott, 1st Duke of Monmouth, equipmentQuality, largely ill-equipped]
-
A.
equipmentIssue
Indicates that there is a problem, malfunction, or defect affecting a piece of equipment.
-
B.
equipmentIncludes
Indicates that one entity contains, comprises, or has as part of its set of items a specified piece or set of equipment.
-
C.
hasEquipmentStatus
chosen
Indicates the current operational or condition state assigned to a piece of equipment.
-
D.
equipmentProvider
Indicates that one entity supplies or makes available equipment for use by another entity.
-
E.
kitAvailability
Indicates that a particular kit is available for use, access, or distribution in a given context.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6609704a88190b0e03463d30b473f |
completed | May 2, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 10:14 a.m.