Triple
T38429447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D400–D449 |
E903757
|
entity |
| Predicate | highestNumber |
P29667
|
FINISHED |
| Object | D449 |
—
|
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: D449 | Statement: [D400–D449, highestNumber, D449]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestNumber Context triple: [D400–D449, highestNumber, D449]
-
A.
maximumNumber
chosen
Indicates that one entity specifies the highest allowable or observed quantity, value, or count associated with another entity.
-
B.
highestElement
Indicates that one element in a set or collection has a value greater than or equal to all other elements according to a specified ordering.
-
C.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
-
D.
maximumDigit
Indicates that one entity is the largest-valued digit present within another entity (such as a number or digit sequence).
-
E.
highestPart
Indicates that one entity is the topmost or uppermost portion 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 3, 2026, 4:31 p.m.