Triple
T30749271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberty Properties |
E782907
|
entity |
| Predicate | hasBrandAssociationWith |
P96602
|
FINISHED |
| Object | Liberty Stadium |
—
|
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: Liberty Stadium | Statement: [Liberty Properties, hasBrandAssociationWith, Liberty Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrandAssociationWith Context triple: [Liberty Properties, hasBrandAssociationWith, Liberty Stadium]
-
A.
hasNotableBrandAssociation
chosen
Indicates that there is a significant, recognizable, or influential brand linked or connected to the subject entity.
-
B.
brandAssociationType
Indicates the specific nature of the relationship or association that exists between a brand and another entity (such as a product, organization, or campaign).
-
C.
hasBrandRole
Indicates that an entity holds a specific functional or organizational role in relation to a particular brand.
-
D.
associatedBrandCategory
Indicates that a brand is linked to or classified under a particular product or service category.
-
E.
associatedBrandMarket
Indicates that a brand is linked to, operates in, or targets a particular market.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 8:38 p.m.