Triple
T21386157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ジョー・ローゼンタール |
E527502
|
entity |
| Predicate | 代表作の用途 |
P80354
|
FINISHED |
| Object | アメリカ海兵隊戦争記念碑の元となったイメージ |
—
|
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: アメリカ海兵隊戦争記念碑の元となったイメージ | Statement: [ジョー・ローゼンタール, 代表作の用途, アメリカ海兵隊戦争記念碑の元となったイメージ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 代表作の用途 Context triple: [ジョー・ローゼンタール, 代表作の用途, アメリカ海兵隊戦争記念碑の元となったイメージ]
-
A.
notableWorkUsed
chosen
Indicates that a particular notable work is utilized, referenced, or incorporated in relation to another entity or context.
-
B.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
isUsedToIllustrate
Indicates that one entity serves as an example or demonstration to clarify, explain, or represent another entity.
-
D.
usedForProduct
Indicates that one entity serves as a tool, component, or means specifically employed in the creation, operation, or delivery of another entity considered as a product.
-
E.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of 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_69e0b51f363c8190944000ab5523b02b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0f3d37c8190b43ec77cdb1904c8 |
completed | April 22, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:12 p.m.