Triple
T24613469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sue clan |
E609182
|
entity |
| Predicate | influenceDeclinedUnder |
P2924
|
FINISHED |
| Object | Chōshū Domain |
—
|
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: Chōshū Domain | Statement: [Sue clan, influenceDeclinedUnder, Chōshū Domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influenceDeclinedUnder Context triple: [Sue clan, influenceDeclinedUnder, Chōshū Domain]
-
A.
declineTriggeredBy
Indicates that a decline event or state is caused or initiated by a specified triggering factor or condition.
-
B.
declineBeganUnder
Indicates that a period of decline started during the tenure, rule, or administration of a specified entity.
-
C.
declineAfter
Indicates that one entity or value decreases or worsens following another specified event, condition, or point in time.
-
D.
declinedDuring
chosen
Indicates that one entity’s value, condition, or status decreased over the course of a specified time period or event.
-
E.
declinedAround
Indicates that something decreased in value, intensity, or quantity in the time period surrounding a specified point or event.
- 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_69e2c4d1140081909c58667bf68f80c3 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:31 a.m.