Triple
T11462365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panther |
E271691
|
entity |
| Predicate | approximateProductionNumber |
P99700
|
FINISHED |
| Object | about 6000 units |
—
|
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 6000 units | Statement: [Panther, approximateProductionNumber, about 6000 units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateProductionNumber Context triple: [Panther, approximateProductionNumber, about 6000 units]
-
A.
designedApproximately
Indicates that one entity was created, planned, or engineered to an estimated or imprecise degree in relation to another entity or specification.
-
B.
approximateWeightInPounds
Indicates the estimated weight of an entity expressed in pounds, rather than an exact measured value.
-
C.
approximateMass
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
D.
massProduced
Indicates that an item is manufactured in large quantities, typically using standardized, industrial production processes.
-
E.
areEstimatedIn
Indicates that a value or quantity is approximated or inferred within a specified context, framework, or unit.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f384f08190b1150ed1389dd31a |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:35 p.m.