Triple
T12936737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Division |
E309529
|
entity |
| Predicate | isOrganizedAccordingTo |
P4786
|
FINISHED |
| Object | British Army divisional structure |
—
|
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: British Army divisional structure | Statement: [Scottish Division, isOrganizedAccordingTo, British Army divisional structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOrganizedAccordingTo Context triple: [Scottish Division, isOrganizedAccordingTo, British Army divisional structure]
-
A.
organizedAs
chosen
Indicates how elements are structured, arranged, or grouped according to a particular organizing principle or scheme.
-
B.
isNotOrganizedAs
Indicates that an entity does not follow, conform to, or exist in the specified organizational structure or arrangement.
-
C.
organizedUnderRulesOf
Indicates that an activity, process, or entity is structured, governed, or conducted according to a specified set of rules or regulations.
-
D.
organizesInto
Indicates that one entity arranges, structures, or groups another entity into a particular order, system, or set of categories.
-
E.
organizedAt
Indicates that an event or activity was arranged, planned, or hosted at a specific location or venue.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.