Triple
T2106113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamon |
E42397
|
entity |
| Predicate | hasTypeOfFind |
P16808
|
FINISHED |
| Object | inscribed artifacts |
—
|
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: inscribed artifacts | Statement: [Lamon, hasTypeOfFind, inscribed artifacts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfFind Context triple: [Lamon, hasTypeOfFind, inscribed artifacts]
-
A.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
B.
containsFinding
Indicates that one entity includes, encompasses, or holds a particular finding as part of its content or results.
-
C.
hasTypeOfCase
Indicates that an entity is associated with or classified under a particular type or category of case.
-
D.
hasTypeOfResource
Indicates that an entity is associated with a specific category or kind of resource it represents or utilizes.
-
E.
requiresFinding
Indicates that one entity’s validity, execution, or completion is contingent upon a specific finding or determination being made about 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbaddeb148190b728bce7a7b041fb |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.