Triple
T11593452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sengaku-ji |
E274940
|
entity |
| Predicate | hasObjectOnDisplay |
P5510
|
FINISHED |
| Object | armour and weapons of the Forty-seven Rōnin |
—
|
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: armour and weapons of the Forty-seven Rōnin | Statement: [Sengaku-ji, hasObjectOnDisplay, armour and weapons of the Forty-seven Rōnin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObjectOnDisplay Context triple: [Sengaku-ji, hasObjectOnDisplay, armour and weapons of the Forty-seven Rōnin]
-
A.
hasObject
chosen
Indicates that an entity is associated with or possesses a particular object as part of a relationship or action.
-
B.
hasOuterDisplay
Indicates that one entity serves as the external or outward-facing display component of another entity.
-
C.
hasDisplayArea
Indicates that an entity includes or is associated with a specific physical or virtual area used for displaying content or items.
-
D.
hasAircraftOnDisplay
Indicates that an entity exhibits or presents an aircraft as part of a display or collection.
-
E.
hasNumberOfObjects
Indicates that an entity is associated with a specific count or quantity of objects.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8946594348190935106132fd18028 |
completed | April 10, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.