Triple
T36547098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ar-Pharazôn |
E901165
|
entity |
| Predicate | launchesInvasionOf |
P56732
|
FINISHED |
| Object | Aman |
—
|
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: Aman | Statement: [Ar-Pharazôn, launchesInvasionOf, Aman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchesInvasionOf Context triple: [Ar-Pharazôn, launchesInvasionOf, Aman]
-
A.
wasInvadedBy
Indicates that a place or territory was subjected to an incursion or attack carried out by another entity or group.
-
B.
plannedInvasionOf
Indicates that one entity has formulated or organized an invasion targeting another entity.
-
C.
invadedDuring
Indicates that one entity carried out an invasion of another entity within the temporal bounds of a specified event or period.
-
D.
invade
chosen
Indicates entering another entity’s territory or domain, typically by force or without permission, in order to take control or exert dominance.
-
E.
invadesFrom
Indicates that one entity initiates an invasion or aggressive incursion into another entity starting from a specified origin or source location.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:11 p.m.