Triple
T31989632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMI Jericho 941 |
E816827
|
entity |
| Predicate | USMarketName |
P133342
|
FINISHED |
| Object | Baby Eagle |
—
|
NE NERFINISHED |
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: Baby Eagle | Statement: [IMI Jericho 941, USMarketName, Baby Eagle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USMarketName Context triple: [IMI Jericho 941, USMarketName, Baby Eagle]
-
A.
USMarketIntroduction
Indicates the event or action of introducing or launching something into the United States market for the first time.
-
B.
marketNameInUnitedStates
chosen
Indicates that an entity’s name or designation as used in the United States market is being specified.
-
C.
marketNameInNorthAmerica
Indicates the specific name under which something is marketed within the North American region.
-
D.
marketShareUS
Indicates the proportion of a product, company, or brand’s total sales or volume within the United States market relative to the overall U.S. market size.
-
E.
marketsIn
Indicates that one entity promotes, sells, or offers another entity’s products or services within a particular market or geographic area.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3b3c128819088fbbf04ffb3b3ec |
completed | May 3, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:13 a.m.