Triple
T25382345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pietroasele Treasure |
E631423
|
entity |
| Predicate | currentNumberOfObjects |
P48434
|
FINISHED |
| Object | approximately half of original |
—
|
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: approximately half of original | Statement: [Pietroasele Treasure, currentNumberOfObjects, approximately half of original]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentNumberOfObjects Context triple: [Pietroasele Treasure, currentNumberOfObjects, approximately half of original]
-
A.
hasNumberOfObjects
chosen
Indicates that an entity is associated with a specific count or quantity of objects.
-
B.
currentNumberOfClasses
Indicates the present count of classes associated with or contained by a given entity.
-
C.
numberOfCounts
Indicates the total quantity or tally of discrete occurrences, items, or instances associated with an entity or event.
-
D.
numberOfEntries
Indicates the total count of individual items, records, or instances associated with a given entity or context.
-
E.
numberOfEntities
Indicates the total count of distinct entities involved in or associated with a given context or situation.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 21, 2026, 1:46 p.m.