Triple
T9379347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borderline |
E225740
|
entity |
| Predicate | complementsNarrativeOf |
P15616
|
FINISHED |
| Object | Travelogue |
—
|
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: Travelogue | Statement: [Borderline, complementsNarrativeOf, Travelogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complementsNarrativeOf Context triple: [Borderline, complementsNarrativeOf, Travelogue]
-
A.
complements
Indicates that one entity enhances, completes, or improves another by providing qualities or functions that fit well together.
-
B.
supportsNarrativeOf
chosen
Indicates that one entity provides evidence, context, or structure that upholds, reinforces, or advances the storyline or interpretive account expressed by another entity.
-
C.
complement
Indicates that one entity completes, enhances, or makes another entity whole or more effective by providing what it lacks.
-
D.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
E.
narratorCompanion
Indicates that one entity serves as a companion or close associate to the narrator within the context of a narrative or account.
- 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_69ca842d8ee88190aaaa639aa953185d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50bb49bc8190bdad23e120755ac7 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:44 p.m.