Triple
T37186494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capaci |
E921333
|
entity |
| Predicate | internationallyKnownFor |
P170102
|
FINISHED |
| Object | Capaci bombing |
—
|
NE NERFINISHED |
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: Capaci bombing | Statement: [Capaci, internationallyKnownFor, Capaci bombing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internationallyKnownFor Context triple: [Capaci, internationallyKnownFor, Capaci bombing]
-
A.
madeInternationallyFamousBy
chosen
Indicates that one entity became widely known across multiple countries as a result of the actions, influence, or association of another entity.
-
B.
nowKnownFor
Indicates that an entity is currently recognized or notable for a particular role, attribute, achievement, or association.
-
C.
alsoKnownFor
Indicates that an entity is additionally recognized or noted for another work, role, achievement, or characteristic beyond its primary association.
-
D.
formerlyKnownFor
Indicates that an entity was previously recognized or notable for a particular role, attribute, or activity, but is no longer primarily associated with it.
-
E.
knownForAct
Indicates that an entity is recognized or notable for performing a particular act or action.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 3, 2026, 4:15 p.m.