Triple
T25277610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heptapods |
E633742
|
entity |
| Predicate | writingIsSimultaneous |
P158326
|
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: [Heptapods, writingIsSimultaneous, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingIsSimultaneous Context triple: [Heptapods, writingIsSimultaneous, true]
-
A.
usesWriting
Indicates that one entity employs or applies a particular writing system, script, or written form for communication or representation.
-
B.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
-
C.
writingTasks
Indicates that an entity is responsible for or engaged in performing writing-related tasks for another entity or context.
-
D.
traditionalWritingStatus
Indicates the status or condition of something with respect to its use of traditional writing forms or scripts.
-
E.
writingsStatus
Indicates the status or condition of a set of writings (e.g., whether they are drafted, reviewed, published, or otherwise processed) in relation to an entity.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48ba8e99081908b3fd911e8634dcc |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f465699c9c8190ac7b4b32b782550c |
completed | May 1, 2026, 8:33 a.m. |
Created at: April 21, 2026, 1:18 p.m.