Triple
T30551332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sutekh division |
E777566
|
entity |
| Predicate | parallelUnit |
P171298
|
FINISHED |
| Object | Amun division |
—
|
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: Amun division | Statement: [Sutekh division, parallelUnit, Amun division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelUnit Context triple: [Sutekh division, parallelUnit, Amun division]
-
A.
parallel
Indicates that two or more entities maintain a constant separation and direction without intersecting or converging.
-
B.
parallelType
Indicates that one entity runs in parallel to another, specifying the type or manner of their parallel relationship.
-
C.
parallelSeeTo
Indicates that one entity observes or attends to another entity in a manner that is simultaneous or coordinated with a comparable act of seeing by a different entity.
-
D.
parallelService
Indicates that two or more services operate concurrently or in parallel rather than sequentially.
-
E.
parallelEvent
Indicates that two or more events occur at the same time or overlap in time without a required order between them.
- 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69dfbf6ac8190ba2e6fc0adfd8b73 |
completed | May 3, 2026, 12:59 a.m. |
Created at: April 29, 2026, 8:20 p.m.