Triple
T27421664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bete Lehem |
E693059
|
entity |
| Predicate | inscriptionLevel |
P164505
|
FINISHED |
| Object | international |
—
|
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: international | Statement: [Bete Lehem, inscriptionLevel, international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionLevel Context triple: [Bete Lehem, inscriptionLevel, international]
-
A.
enrollmentLevel
Indicates the degree or status of participation an entity has in a particular enrollment context (such as a program, course, or service).
-
B.
inscriptionStatus
Indicates the current state or condition of an inscription, such as whether it has been created, verified, updated, or removed.
-
C.
qualificationLevel
Indicates the degree or rank of competence, certification, or formal credentials required for or possessed in relation to something.
-
D.
initiationLevels
Indicates the degree or stage at which an action, process, or relationship is begun or set in motion between entities.
-
E.
inscriptionBy
Indicates that an inscription was created, written, or carved by a particular agent or entity.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 12:36 p.m.