Triple
T26820834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lions Lighthouse for Sight |
E675242
|
entity |
| Predicate | nonOperational |
P2509
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lions Lighthouse for Sight, nonOperational, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonOperational Context triple: [Lions Lighthouse for Sight, nonOperational, true]
-
A.
doesNotOperate
chosen
Indicates that an entity is not functioning, active, or performing its intended operation in relation to another entity or context.
-
B.
nonProfessional
Indicates that the relationship or activity is carried out in an informal or amateur capacity rather than as part of a recognized profession or paid occupation.
-
C.
normallyOperatesAs
Indicates that an entity’s usual or standard mode, role, or state of functioning is as the specified other entity or type.
-
D.
notStatus
Indicates that an entity does not have, is not in, or does not match a specified status or state.
-
E.
nonConstructive
Indicates that the relationship or action does not provide a direct, explicit method or example to realize or build the object, outcome, or proof it asserts exists.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61a89d73c8190b1287cab1ce69805 |
completed | May 2, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 4:55 a.m.