Triple
T36887093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Crotone |
E911638
|
entity |
| Predicate | traditionalTactic |
P1716
|
FINISHED |
| Object | attacking style in lower leagues |
—
|
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: attacking style in lower leagues | Statement: [FC Crotone, traditionalTactic, attacking style in lower leagues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalTactic Context triple: [FC Crotone, traditionalTactic, attacking style in lower leagues]
-
A.
tacticOf
Indicates that one entity is a tactic, method, or strategy employed or used by another entity.
-
B.
tactic
chosen
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
C.
traditionalRule
Indicates that an entity follows, embodies, or is governed by a customary or long-established rule or norm.
-
D.
traditionalSee
Indicates that one entity perceives or views another entity in a conventional or customary manner, following established norms or traditions.
-
E.
traditionalBase
Indicates that one entity serves as the customary or historically established foundation or basis for another.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffac35ac5481908b6bdfd5bbe8c76e |
completed | May 9, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69ffabbfd2548190964c851496bbbaee |
completed | May 9, 2026, 9:48 p.m. |
Created at: May 3, 2026, 4:13 p.m.