Triple
T16193102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oculi Exercitus |
E392991
|
entity |
| Predicate | reflectsRoleIn |
P57555
|
FINISHED |
| Object | aerial reconnaissance |
—
|
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: aerial reconnaissance | Statement: [Oculi Exercitus, reflectsRoleIn, aerial reconnaissance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsRoleIn Context triple: [Oculi Exercitus, reflectsRoleIn, aerial reconnaissance]
-
A.
reflectsRoleAs
chosen
Indicates that one entity expresses, represents, or makes evident the role, function, or position held by another entity.
-
B.
refersToRole
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
-
C.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
D.
acknowledgesRoleOf
Indicates that one entity explicitly recognizes and accepts the position, function, or authority that another entity holds.
-
E.
representedRole
Indicates that one entity serves as a stand-in, proxy, or representative performing a role on behalf of another entity.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222d74d788190a637fdb9b4f184b9 |
completed | April 17, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.