Triple
T2114198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AES-CTR |
E42568
|
entity |
| Predicate | isParallelizable |
P34884
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [AES-CTR, isParallelizable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isParallelizable Context triple: [AES-CTR, isParallelizable, true]
-
A.
hasParallelBody
Indicates that one entity’s body is oriented in a direction parallel to the body of another entity.
-
B.
hasParallelTransit
Indicates that one transit route, service, or segment runs in parallel to another along a similar path or corridor.
-
C.
followsParallel
Indicates that one entity proceeds in the same general direction or sequence as another, maintaining a parallel course or progression without necessarily intersecting.
-
D.
parallelSubdivision
Indicates that one structure or process is divided into multiple parts that proceed or are handled simultaneously alongside each other.
-
E.
hasParallelReporter
Indicates that a legal case or decision has an alternative citation or report in a different reporter series that runs in parallel to the primary one.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb05b51c81908a78c816f492c45c |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:43 p.m.