Triple
T24498987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scattery Island |
E617877
|
entity |
| Predicate | hasNumberOfChurchRuins |
P156534
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [Scattery Island, hasNumberOfChurchRuins, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfChurchRuins Context triple: [Scattery Island, hasNumberOfChurchRuins, 6]
-
A.
hasMonasteryRuins
Indicates that an entity possesses or contains the remains or ruins of a former monastery.
-
B.
originalChurchDestroyed
Indicates that the initially established church building was demolished or ceased to exist, typically due to destruction rather than relocation or replacement.
-
C.
hasReconstructedChurch
Indicates that an entity has rebuilt or restored a church, typically after damage, destruction, or disuse.
-
D.
hasRuin
Indicates that one entity possesses, contains, or is associated with a ruin or ruined structure.
-
E.
hasPilgrimageChurch
Indicates that a location or entity possesses or is associated with a church that serves as a destination for religious pilgrimage.
- 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_69e2d7f682108190a1a7ca5fd485ee8a |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a9d795288190916368e3cec1f666 |
completed | April 30, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:23 a.m.