Triple
T22591866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orkut |
E564968
|
entity |
| Predicate | supportedAdvertising |
P126840
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Orkut, supportedAdvertising, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedAdvertising Context triple: [Orkut, supportedAdvertising, yes]
-
A.
supportsAdvertising
chosen
Indicates that one entity enables, allows, or is compatible with the display or delivery of advertising for another entity.
-
B.
supportsTargetedAdvertising
Indicates that an entity enables or facilitates the delivery of advertisements tailored to specific users or audience segments based on their data or behavior.
-
C.
usesAdvertisingModel
Indicates that one entity employs or relies on another entity’s advertising-based business or revenue model.
-
D.
includesAdvertisingClause
Indicates that a contract or agreement contains a specific clause governing advertising-related rights, obligations, or restrictions.
-
E.
hasAdvertisingMarket
Indicates that an entity participates in or is associated with a specific advertising market where advertising space, time, or services are bought and sold.
- 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f16162c2cc8190a506776ac52356d7 |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:49 p.m.