Triple
T23269211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagawat necropolis |
E588241
|
entity |
| Predicate | hasApproximateNumberOfChapels |
P16477
|
FINISHED |
| Object | over 200 |
—
|
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: over 200 | Statement: [Bagawat necropolis, hasApproximateNumberOfChapels, over 200]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateNumberOfChapels Context triple: [Bagawat necropolis, hasApproximateNumberOfChapels, over 200]
-
A.
hasChapels
Indicates that one entity contains, includes, or is associated with one or more chapels.
-
B.
hasChapelCountApprox
chosen
Indicates an approximate number of chapels associated with an entity.
-
C.
hasNumberOfChurches
Indicates the relationship that specifies how many churches are associated with a given entity.
-
D.
hasChapelLocation
Indicates that one entity serves as the physical location or site where a chapel associated with another entity is situated.
-
E.
hasChapelNearby
Indicates that one entity is located close to or in the vicinity of a chapel.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957219188190b30bceffad1542da |
completed | April 29, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:45 p.m.