Triple
T35343105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akechi clan |
E1020660
|
entity |
| Predicate | statusUnderOda |
P200270
|
FINISHED |
| Object | vassal |
—
|
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: vassal | Statement: [Akechi clan, statusUnderOda, vassal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusUnderOda Context triple: [Akechi clan, statusUnderOda, vassal]
-
A.
statusUnderARC
Indicates that one entity’s status is defined, governed, or classified according to the rules or framework of an ARC (e.g., a specific regulatory, review, or control system).
-
B.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
C.
ODIStatus
Indicates that an entity’s status or condition is classified according to One Day International (ODI) criteria, typically in the context of cricket matches or teams.
-
D.
statusInSira
Indicates the status or standing that an entity holds within the Sira system or classification.
-
E.
statusUnderASC
Indicates that one entity has a particular accounting or reporting status as defined under ASC (Accounting Standards Codification) relative to another context or framework.
- F. None of above. chosen
Provenance (4 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
| PDg | Predicate description generation | batch_69ff7dce25d88190b167a014661bc4ba |
completed | May 9, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:03 p.m.