Triple
T24278814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2004 Krue Se Mosque incident |
E605482
|
entity |
| Predicate | hasTypeOfTarget |
P16808
|
FINISHED |
| Object | religious building |
—
|
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: religious building | Statement: [2004 Krue Se Mosque incident, hasTypeOfTarget, religious building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfTarget Context triple: [2004 Krue Se Mosque incident, hasTypeOfTarget, religious building]
-
A.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
B.
hasTypeOfReference
Indicates that one entity uses or is associated with a particular kind or category of reference (such as a citation, pointer, or referential link) to another entity.
-
C.
hasTypeOfMatches
Indicates that one entity has matches that are of a specified type or category in relation to another entity.
-
D.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasTypeOfSource
Indicates that one entity is classified as a particular kind or category of source in relation to another entity.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5032f48190a027e2d8b382ee79 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.