Triple
T9962784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papyrus 66 |
E195608
|
entity |
| Predicate | hasLacunae |
P91686
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Papyrus 66, hasLacunae, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLacunae Context triple: [Papyrus 66, hasLacunae, yes]
-
A.
hasVow
Indicates that one entity has made or is bound by a formal vow or promise in relation to another entity or context.
-
B.
hasCadenza
Indicates that a musical work, passage, or performance includes or is associated with a cadenza section.
-
C.
has
Indicates that one entity possesses, owns, contains, or includes another entity as part of its state or composition.
-
D.
hasLobes
Indicates that an entity possesses distinct rounded or projecting parts (lobes) as characteristic features of its form or structure.
-
E.
hasLacing
Indicates a relationship where one entity is fastened, joined, or secured to another using laces or a lacing mechanism.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb718cd588190a4aac48220deddec |
completed | April 2, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd36f112bc81908b473787e702de2f |
completed | April 1, 2026, 3:17 p.m. |
Created at: March 30, 2026, 8:47 p.m.