Triple
T299811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATA |
E6172
|
entity |
| Predicate | parallelOrSerial |
P1868
|
FINISHED |
| Object | parallel |
—
|
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: parallel | Statement: [ATA, parallelOrSerial, parallel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelOrSerial Context triple: [ATA, parallelOrSerial, parallel]
-
A.
parallels
chosen
Indicates that one entity runs alongside or corresponds to another in a way that maintains a consistent separation or similarity without intersecting.
-
B.
parallelGospel
Indicates that one gospel text corresponds closely to another in content, structure, or narrative, allowing them to be compared side by side as parallel accounts.
-
C.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
D.
parallelConference
Indicates that two or more conferences occur at the same time or overlap in schedule, running in parallel to each other.
-
E.
operatedAlongside
Indicates that two or more entities functioned or were active together in a coordinated or concurrent manner within the same context or system.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea0dd1dc8190aecd5afdeb2fd74b |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e9398df08190af40063a2de7a1d0 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.