Triple
T30079891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Outsyders |
E764422
|
entity |
| Predicate | typicalCredit |
P10646
|
FINISHED |
| Object | producer |
—
|
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: producer | Statement: [The Outsyders, typicalCredit, producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCredit Context triple: [The Outsyders, typicalCredit, producer]
-
A.
typicalCreditRequirement
Indicates the usual or standard amount of credit that is generally required or expected in a given context.
-
B.
hasTypeOfCredit
Indicates that an entity is associated with or characterized by a specific type or category of credit.
-
C.
hasCredit
chosen
Indicates that an entity possesses or is assigned a credit, such as financial credit, academic credit, or acknowledgment for a contribution.
-
D.
creditFunction
Indicates a financial role or operation through which an entity extends, manages, or utilizes credit within an economic or transactional context.
-
E.
hasCreditRating
Indicates that an entity is assigned a formal assessment of its creditworthiness, typically expressed as a credit score or rating.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0353887e848190ad98ecbbe7bbc061 |
completed | May 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_6a0352dfb5648190b9f8c9b7c388d2a1 |
completed | May 12, 2026, 4:18 p.m. |
Created at: April 29, 2026, 7:02 p.m.