Triple
T18563835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenician block |
E453711
|
entity |
| Predicate | blockCode |
P9329
|
FINISHED |
| Object | Phoenician |
—
|
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: Phoenician | Statement: [Phoenician block, blockCode, Phoenician]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockCode Context triple: [Phoenician block, blockCode, Phoenician]
-
A.
bodyCode
Indicates that an entity is assigned a specific body-related code used to classify or identify its physical form or condition.
-
B.
codeSection
Indicates a specific segment or subsection within a larger body of code that is distinguished for reference, organization, or analysis.
-
C.
scriptCode
chosen
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
D.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
E.
programmingBlock
Indicates a relationship where one entity is a defined segment or unit of programming logic (such as a code block or script section) associated with or contained within another entity.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afc57448190abd90167d7e12a18 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:42 a.m.