Triple
T1371435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kani Doraku crab sign |
E30119
|
entity |
| Predicate | photographedBy |
P12333
|
FINISHED |
| Object | tourists from around the world |
—
|
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: tourists from around the world | Statement: [Kani Doraku crab sign, photographedBy, tourists from around the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: photographedBy Context triple: [Kani Doraku crab sign, photographedBy, tourists from around the world]
-
A.
photographer
chosen
Indicates that one entity takes photographs of another entity, typically in a professional or intentional capacity.
-
B.
notablePhotographer
Indicates that the subject is a photographer who is recognized as notable or significant in some context.
-
C.
hasPhotograph
Indicates that one entity possesses, includes, or is associated with a photograph depicting or representing another entity.
-
D.
collectedBy
Indicates that one entity has gathered, acquired, or assembled another entity, typically as part of a collection or data-gathering process.
-
E.
capturedBy
Indicates that one entity has been seized, taken into control, or otherwise apprehended by 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2f314c081909c0ab80397d96abb |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befb08b88190be966fa1aadd4bcd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.