Triple
T32303531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | With Her in Ourland |
E825297
|
entity |
| Predicate | literaryContinuationOf |
P20918
|
FINISHED |
| Object | Herland |
—
|
NE NERFINISHED |
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: Herland | Statement: [With Her in Ourland, literaryContinuationOf, Herland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryContinuationOf Context triple: [With Her in Ourland, literaryContinuationOf, Herland]
-
A.
continuedBy
chosen
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
-
B.
literaryPredecessor
Indicates that one work of literature precedes and influences another in a historically or artistically significant way.
-
C.
literarySeries
Indicates that one work is part of, or belongs to, a larger literary series that connects multiple related works.
-
D.
fictionContinuity
Indicates that two or more fictional works share the same narrative continuity, treating events and developments as occurring within a single consistent storyline or universe.
-
E.
textualContinuity
Indicates that one text segment continues, follows, or is sequentially connected to another in the flow of discourse or narrative.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: May 1, 2026, 12:45 a.m.