Triple
T15640970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman numeral system |
E376061
|
entity |
| Predicate | typicalMaximumStandardNumber |
P29667
|
FINISHED |
| Object | 3999 |
—
|
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: 3999 | Statement: [Roman numeral system, typicalMaximumStandardNumber, 3999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMaximumStandardNumber Context triple: [Roman numeral system, typicalMaximumStandardNumber, 3999]
-
A.
standardNumber
Indicates that an entity is associated with a canonical or officially recognized reference number used for identification or classification.
-
B.
maximumNumber
chosen
Indicates that one entity specifies the highest allowable or observed quantity, value, or count associated with another entity.
-
C.
typicalMaximumAge
Indicates the usual upper age limit that an entity is expected or allowed to reach under normal conditions.
-
D.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
E.
typicalHighestLevel
Indicates the usual or most common maximum level or degree that something typically reaches within a given context.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed06b388190bfebb77fe70e7df1 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.