Triple
T440378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MGM |
E10100
|
entity |
| Predicate | notableLogo |
P3488
|
FINISHED |
| Object | roaring lion logo |
—
|
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: roaring lion logo | Statement: [MGM, notableLogo, roaring lion logo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLogo Context triple: [MGM, notableLogo, roaring lion logo]
-
A.
notableProduct
Indicates that a product is especially significant, prominent, or well-known in relation to the associated entity.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
notableAsset
chosen
Indicates that an entity possesses or is associated with an asset that is particularly significant, prominent, or noteworthy in relation to it.
-
D.
notableOrganizationWithin
Indicates that one organization is a prominent or significant entity operating within the scope, structure, or domain of another organization.
-
E.
notableBase
Indicates that a particular location serves as a significant or distinguished base or headquarters for an 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef2977888190a0590b2c1bd2f5da |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2eddcf50c8190bfa0d1f8ee9f604a |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.