Triple
T19693748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Four record companies |
E472898
|
entity |
| Predicate | typicalContracts |
P15887
|
FINISHED |
| Object | multi-album recording contracts |
—
|
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: multi-album recording contracts | Statement: [Big Four record companies, typicalContracts, multi-album recording contracts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalContracts Context triple: [Big Four record companies, typicalContracts, multi-album recording contracts]
-
A.
typeOfContract
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
B.
notableContract
Indicates that there exists a contract or agreement between entities that is of particular significance, prominence, or public interest.
-
C.
typicalLegalForm
Indicates the standard or commonly used legal organizational form associated with an entity.
-
D.
contractUnit
Indicates that one entity serves as a contractual unit or party within a contract relationship involving another entity.
-
E.
contractFeature
chosen
Indicates that one entity is a feature, term, or provision that is included in or associated with a particular contract.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e64211e5d481908358d922e0dca271 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.