Triple
T35552830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiei |
E1027410
|
entity |
| Predicate | laterRearmed |
P202308
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hiei, laterRearmed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRearmed Context triple: [Hiei, laterRearmed, yes]
-
A.
laterArm
Indicates that one event, state, or action occurs at a later time than another within the same arm or branch of a process or study.
-
B.
laterRestored
Indicates that something previously altered, damaged, or removed was subsequently brought back to its earlier state or condition.
-
C.
laterRepurposedFor
Indicates that something was originally used for one purpose and subsequently assigned a different, new purpose.
-
D.
laterWeaponizedBy
Indicates that something was subsequently developed, adapted, or used as a weapon by a specified agent or group.
-
E.
laterDeployedIn
Indicates that one entity was deployed or put into operation in a particular context, location, or system at a later time than another.
- 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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00708ab11081909641d245c4282aa0 |
completed | May 10, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_6a00703daa0081908903ce3a28084d35 |
completed | May 10, 2026, 11:47 a.m. |
| PDg | Predicate description generation | batch_6a00708a01d08190a290fabcb435c358 |
completed | May 10, 2026, 11:48 a.m. |
Created at: May 3, 2026, 4:04 p.m.