Triple
T151829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Warner |
E3446
|
entity |
| Predicate | notableAssetType |
P3488
|
FINISHED |
| Object | film studio |
—
|
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: film studio | Statement: [Time Warner, notableAssetType, film studio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAssetType Context triple: [Time Warner, notableAssetType, film studio]
-
A.
notableAsset
chosen
Indicates that an entity possesses or is associated with an asset that is particularly significant, prominent, or noteworthy in relation to it.
-
B.
primaryAsset
Indicates that one entity is the main or most important asset associated with another entity.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
notableHolder
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
-
E.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580f55a88190b37b54ee0ed5ac7c |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565adaf48190b68ae4444ff83ccd |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.