Triple
T25277609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heptapods |
E633742
|
entity |
| Predicate | hasWritingAppearance |
P93281
|
FINISHED |
| Object | circular logograms |
—
|
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: circular logograms | Statement: [Heptapods, hasWritingAppearance, circular logograms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWritingAppearance Context triple: [Heptapods, hasWritingAppearance, circular logograms]
-
A.
isWritten
Indicates that a text, document, or content has been created or recorded in written form by an agent.
-
B.
hasWritingType
chosen
Indicates that one entity is associated with, or characterized by, a particular type or form of writing.
-
C.
hasWrittenForm
Indicates that an entity is associated with a specific written or textual representation.
-
D.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
-
E.
hasWrittenFor
Indicates that one entity has created written content (such as articles, stories, or texts) for or on behalf of another entity, typically a publication, organization, or platform.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 1:18 p.m.