Triple
T17085730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eciton |
E414591
|
entity |
| Predicate | raidingPattern |
P125826
|
FINISHED |
| Object | organized columns |
—
|
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: organized columns | Statement: [Eciton, raidingPattern, organized columns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raidingPattern Context triple: [Eciton, raidingPattern, organized columns]
-
A.
raidedRegion
Indicates that an agent carried out a raid targeting or occurring within a specified region.
-
B.
associatedRaid
Indicates a relationship where one entity is linked to or involved with a particular raid event or operation.
-
C.
majorRaid
Indicates a large-scale, coordinated attack or incursion carried out against a target.
-
D.
hasRaid
Indicates that an entity is associated with, participates in, or is the target of a raid event or operation.
-
E.
sacrificePattern
Indicates a recurring way in which one entity gives up or endures loss of something valuable for the benefit, protection, or advantage of another.
- F. None of above. chosen
Provenance (4 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe6d5288190bdaec41c642d52a2 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:35 a.m.