Triple
T29399171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 額田王 |
E745586
|
entity |
| Predicate | 記録される史料 |
P112143
|
FINISHED |
| Object | 万葉集 |
—
|
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: 万葉集 | Statement: [額田王, 記録される史料, 万葉集]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 記録される史料 Context triple: [額田王, 記録される史料, 万葉集]
-
A.
historicalRecord
Indicates that there exists a documented account or record capturing information about an entity, event, or relationship from the past.
-
B.
historicalMaterial
chosen
Indicates that something serves as a source or document providing information or evidence about past events or conditions.
-
C.
historicalResource
Indicates that a resource has historical significance or relevance, typically documenting or representing past events, conditions, or contexts.
-
D.
historicalEvidence
Indicates that there exists documented or otherwise verifiable information supporting the occurrence, authenticity, or truth of a past event, state, or relationship between entities.
-
E.
areRecordedBy
Indicates that an event, observation, or piece of information is captured or documented by a specific recording agent, device, or process.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a055e9c8190b8e779d7f75eafa2 |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:49 p.m.