Triple
T26337889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor Eremita |
E662566
|
entity |
| Predicate | usedInAuthorStrategy |
P172770
|
FINISHED |
| Object | indirect communication |
—
|
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: indirect communication | Statement: [Victor Eremita, usedInAuthorStrategy, indirect communication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInAuthorStrategy Context triple: [Victor Eremita, usedInAuthorStrategy, indirect communication]
-
A.
usedByAuthor
Indicates that something (such as a method, tool, or resource) is employed or utilized by an author.
-
B.
usedByAuthorTo
Indicates that something is employed or utilized by an author to achieve a particular purpose or effect.
-
C.
canonicalAuthor
Indicates that an entity is the officially recognized or standard author of a given work or resource.
-
D.
positionOfAuthor
Indicates the spatial or organizational location associated with an author in relation to some reference context.
-
E.
hasAuthorField
Indicates that an entity includes a designated field or attribute for specifying its author.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 26, 2026, 10:37 p.m.