Triple
T9423119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nail from the True Cross |
E227203
|
entity |
| Predicate | hasMultipleClaimedSpecimens |
P88794
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [nail from the True Cross, hasMultipleClaimedSpecimens, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleClaimedSpecimens Context triple: [nail from the True Cross, hasMultipleClaimedSpecimens, true]
-
A.
hasNotableSpecimen
Indicates that an entity possesses or is associated with a specimen that is considered particularly significant, remarkable, or noteworthy.
-
B.
hasLivingSpecimens
Indicates that there currently exist one or more living examples or instances of the related entity.
-
C.
isTypeSpecimen
Indicates that an entity serves as the designated type specimen upon which the formal description and name of a taxon are based.
-
D.
hasExhibitSpecies
Indicates that an exhibit or display includes or features a particular species.
-
E.
hasClaimOn
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd6c27c8cc8190a11162c10c33b17e |
completed | April 1, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:48 p.m.