Triple
T28722645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gregory–Aland 𝔓46 |
E730135
|
entity |
| Predicate | estimatedOriginalLeaves |
P20098
|
FINISHED |
| Object | about 104 leaves |
—
|
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: about 104 leaves | Statement: [Gregory–Aland 𝔓46, estimatedOriginalLeaves, about 104 leaves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedOriginalLeaves Context triple: [Gregory–Aland 𝔓46, estimatedOriginalLeaves, about 104 leaves]
-
A.
originalNumberOfLeaves
chosen
Indicates the initial count of leaves associated with an entity before any changes, losses, or additions occur.
-
B.
leavesIn
Indicates that one entity departs from or exits another entity, such as a place, group, or state, at a particular time or under certain conditions.
-
C.
estimatedOriginalLength
Indicates the approximated or inferred length that something originally had before any changes, damage, or loss.
-
D.
currentNumberOfLeaves
Indicates the present count of leaves associated with an entity at a given point in time.
-
E.
hasApproximateLeaves
Indicates that one entity possesses a number of leaves that is approximately equal to the number of leaves of 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 5:54 a.m.