Triple
T37989986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the lighthouse (symbol in To the Lighthouse) |
E947797
|
entity |
| Predicate | revisitedInSection |
P189618
|
FINISHED |
| Object | Time Passes |
—
|
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: Time Passes | Statement: [the lighthouse (symbol in To the Lighthouse), revisitedInSection, Time Passes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revisitedInSection Context triple: [the lighthouse (symbol in To the Lighthouse), revisitedInSection, Time Passes]
-
A.
rememberedInSection
chosen
Indicates that something is recalled, referenced, or commemorated within a specific section of a document, text, or work.
-
B.
reopenedSection
Indicates that a previously closed or inactive section has been opened again and returned to active or accessible status.
-
C.
openedInSection
Indicates that something was opened or initiated within a specific section or subsection of a larger structure or context.
-
D.
operatorInSection
Indicates that an operator is assigned to, works within, or is responsible for a specific section.
-
E.
relocatedSection
Indicates that a section has been moved from its original location to a new location within a structure or document.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.