Triple
T30842684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exiles series |
E785553
|
entity |
| Predicate | hasAccompanyingTextBy |
P81389
|
FINISHED |
| Object | various essayists and critics |
—
|
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: various essayists and critics | Statement: [Exiles series, hasAccompanyingTextBy, various essayists and critics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccompanyingTextBy Context triple: [Exiles series, hasAccompanyingTextBy, various essayists and critics]
-
A.
hasCompanionInText
Indicates that one entity is accompanied by or associated with another entity within the same textual context or passage.
-
B.
hasTextBy
chosen
Indicates that one entity (such as a document, work, or record) contains or is associated with text authored or written by another entity.
-
C.
hasText
Indicates that an entity is associated with or contains a specific piece of textual content.
-
D.
associatedWithText
Indicates that an entity has a contextual or semantic connection to a specific piece of text.
-
E.
hasTextFrom
Indicates that one entity contains, is derived from, or directly uses the textual content originating from 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 29, 2026, 8:45 p.m.