Triple
T25569763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byblos |
E640940
|
entity |
| Predicate | heritageID |
P48054
|
FINISHED |
| Object | 295 |
—
|
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: 295 | Statement: [Byblos, heritageID, 295]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageID Context triple: [Byblos, heritageID, 295]
-
A.
heritageId
chosen
Indicates that one entity serves as the heritage identifier or heritage reference code associated with another entity.
-
B.
heritageReference
Indicates that one entity serves as a cultural, historical, or heritage-related reference or source for another entity.
-
C.
heritageSystem
Indicates that one entity functions as a heritage or legacy system in relation to another, typically as an older or foundational technological system that the other depends on, interfaces with, or is intended to replace.
-
D.
heritageService
Indicates that an entity provides, manages, or is associated with services related to the preservation, interpretation, or promotion of cultural or natural heritage.
-
E.
isPartOfHeritage
Indicates that something belongs to, contributes to, or is recognized as a component of a broader cultural, historical, or natural heritage.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 3:56 p.m.