Triple
T6493523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grosse Point Lighthouse |
E148097
|
entity |
| Predicate | functionStatus |
P71051
|
FINISHED |
| Object | preserved |
—
|
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: preserved | Statement: [Grosse Point Lighthouse, functionStatus, preserved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionStatus Context triple: [Grosse Point Lighthouse, functionStatus, preserved]
-
A.
returnStatus
Indicates the current outcome or condition of a previously initiated return action or process.
-
B.
exportStatus
Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
-
C.
programStatus
Indicates the current state or condition of a program within its lifecycle (e.g., planned, active, paused, completed, or terminated).
-
D.
formulaStatus
Indicates the current state or condition of a formula, such as whether it is valid, active, pending, or otherwise classified in a workflow or system.
-
E.
automationStatus
Indicates whether a process, task, or system is being performed automatically or requires manual intervention.
- 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06ab6abbc8190a4971ad5a654b0cd |
completed | March 22, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c067f1ef148190bc0355abe83f7e16 |
completed | March 22, 2026, 10:06 p.m. |
Created at: March 22, 2026, 4:53 p.m.