Triple
T28397319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palaiochora, Aegina |
E719314
|
entity |
| Predicate | hasApproximateNumberOfChurches |
P12144
|
FINISHED |
| Object | around 30 |
—
|
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: around 30 | Statement: [Palaiochora, Aegina, hasApproximateNumberOfChurches, around 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateNumberOfChurches Context triple: [Palaiochora, Aegina, hasApproximateNumberOfChurches, around 30]
-
A.
hasNumberOfChurches
chosen
Indicates the relationship that specifies how many churches are associated with a given entity.
-
B.
hasParishChurchesIn
Indicates that an entity possesses or is associated with one or more parish churches located within a specified area or jurisdiction.
-
C.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
D.
hasMemberChurchesIn
Indicates that an organization or group includes member churches that are located within a specified geographic area or jurisdiction.
-
E.
hasReplicaChurch
Indicates that an entity has a church that is a replica or reproduction of it.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 28, 2026, 1:17 a.m.