Triple
T30905912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Insula Șerpilor |
E787299
|
entity |
| Predicate | lighthouseRebuiltBy |
P147295
|
FINISHED |
| Object | Russian Empire |
—
|
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: Russian Empire | Statement: [Insula Șerpilor, lighthouseRebuiltBy, Russian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lighthouseRebuiltBy Context triple: [Insula Șerpilor, lighthouseRebuiltBy, Russian Empire]
-
A.
lighthouseRebuilt
Indicates that a lighthouse, previously existing, has been reconstructed or built again after damage, destruction, or decommissioning.
-
B.
lighthouseConstructedIn
Indicates that a lighthouse was built or established during a specific time period or in a specific year.
-
C.
lighthouseMaintainedBy
Indicates that a lighthouse is operated, serviced, or kept in working condition by a particular person, organization, or authority.
-
D.
lighthouseBuilder
chosen
Indicates that one entity is the builder or constructor responsible for creating a lighthouse associated with another entity.
-
E.
lighthouseType
Indicates the specific classification or category of a lighthouse based on its design, function, or operational characteristics.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 8:50 p.m.