Triple
T32972391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swingville |
E843558
|
entity |
| Predicate | relationshipToPrestige |
P205218
|
FINISHED |
| Object | subsidiary imprint |
—
|
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: subsidiary imprint | Statement: [Swingville, relationshipToPrestige, subsidiary imprint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToPrestige Context triple: [Swingville, relationshipToPrestige, subsidiary imprint]
-
A.
perceivedPrestigeLevel
Indicates the degree to which something is regarded as prestigious or high-status in the eyes of observers.
-
B.
isPrestigiousIn
Indicates that an entity is widely recognized and highly regarded for excellence or status within a particular field, domain, or context.
-
C.
relationshipReputation
Indicates how one entity’s standing, trustworthiness, or esteem is perceived by another entity or within a given context.
-
D.
morePrestigiousThan
Indicates that one entity is regarded as having higher status, esteem, or prestige than another.
-
E.
hasReputationAmong
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037cab06288190b093935f235ddff2 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:21 a.m.