Triple
T30056658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survive the Summer |
E763750
|
entity |
| Predicate | describesCreativeReturnAfter |
P180340
|
FINISHED |
| Object | label disputes |
—
|
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: label disputes | Statement: [Survive the Summer, describesCreativeReturnAfter, label disputes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesCreativeReturnAfter Context triple: [Survive the Summer, describesCreativeReturnAfter, label disputes]
-
A.
conditionOfReturn
Indicates the specific terms or requirements under which something that was previously given, lent, or transferred must be returned.
-
B.
returnDescription
Indicates that an entity provides or yields a description or explanatory information about something.
-
C.
reasonForReturn
Indicates the reason or cause why an item, product, or entity is being sent back or returned.
-
D.
refundPolicy
Indicates the terms and conditions under which payments are returned or compensated after a purchase or transaction.
-
E.
returnedToUse
Indicates that something previously inactive, unavailable, or discontinued has been put back into active use or operation.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
| PDg | Predicate description generation | batch_69f73adfd9a081908adae6bd59dfefb9 |
completed | May 3, 2026, 12:09 p.m. |
Created at: April 29, 2026, 6:56 p.m.