Triple
T29900120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradox Engine |
E759385
|
entity |
| Predicate | setCode |
P168230
|
FINISHED |
| Object | AER |
—
|
NE NERFINISHED |
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: AER | Statement: [Paradox Engine, setCode, AER]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setCode Context triple: [Paradox Engine, setCode, AER]
-
A.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
B.
appliesCode
Indicates that one entity enforces, executes, or puts into effect a specific code, rule set, or coding scheme on another entity or context.
-
C.
bodyCode
Indicates that an entity is assigned a specific body-related code used to classify or identify its physical form or condition.
-
D.
representsCode
Indicates that one entity serves as a code, encoding, or symbolic representation for another entity.
-
E.
scriptCode
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6772e14d48190a9c4dda3d35d0f37 |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:06 p.m.