Triple
T30749172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heritage Hills |
E782902
|
entity |
| Predicate | lendsIdentityTo |
P116141
|
FINISHED |
| Object | Heritage Hills High School |
—
|
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: Heritage Hills High School | Statement: [Heritage Hills, lendsIdentityTo, Heritage Hills High School]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lendsIdentityTo Context triple: [Heritage Hills, lendsIdentityTo, Heritage Hills High School]
-
A.
adoptedIdentity
Indicates that one entity has taken on or assumed the identity, role, or persona of another entity, either formally or informally.
-
B.
transmissionOfIdentity
chosen
Indicates that one entity passes on, confers, or preserves its identity or identifying attributes to or through another entity.
-
C.
publicIdentity
Indicates that an entity’s outward-facing identity or persona is known, presented, or recognized in a public context.
-
D.
killsOnBehalfOf
Indicates that one entity kills another while acting under the direction, authority, or interests of a third party.
-
E.
supportsIdentity
Indicates that one entity upholds, validates, or reinforces the identity, self-concept, or role 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f7053f88190950d9cbc7f455ed2 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:38 p.m.