Triple
T25931718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AESENCLAST |
E653452
|
entity |
| Predicate | operandRole |
P56870
|
FINISHED |
| Object | one source operand |
—
|
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: one source operand | Statement: [AESENCLAST, operandRole, one source operand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operandRole Context triple: [AESENCLAST, operandRole, one source operand]
-
A.
roleInOperation
chosen
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
B.
effectiveRole
Indicates the functional role or capacity an entity actually performs or holds in a given context, regardless of its formal or nominal designation.
-
C.
representedRole
Indicates that one entity serves as a stand-in, proxy, or representative performing a role on behalf of another entity.
-
D.
encodingRole
Indicates the role or function an entity has in the process of encoding information into a particular form or representation.
-
E.
basisRole
Indicates that one role serves as the foundational or underlying role upon which another role or function is defined or derived.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 22, 2026, 8:37 a.m.