Triple
T1611504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InMail |
E34623
|
entity |
| Predicate | creditsAre |
P30264
|
FINISHED |
| Object | limited per billing period |
—
|
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: limited per billing period | Statement: [InMail, creditsAre, limited per billing period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creditsAre Context triple: [InMail, creditsAre, limited per billing period]
-
A.
creditedFor
Indicates that one entity is acknowledged as the source, contributor, or originator responsible for another entity (such as a work, achievement, or outcome).
-
B.
creditedTitle
Indicates that a particular title or role is formally attributed to an entity as a credit.
-
C.
contributors
Indicates that one or more entities have provided work, resources, or input toward the creation, development, or maintenance of another entity.
-
D.
requiresAttribution
Indicates that one entity’s use, display, or distribution of another entity requires giving proper credit or acknowledgment to the original source.
-
E.
originalArtistNameCredit
Indicates that the credited name refers to the artist who originally created the work or recording.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fa6926081908bc78d15c0be3185 |
completed | March 5, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69a907c35f848190a2428c52e81d013e |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a93fa5aa04819084d1154ef900303f |
completed | March 5, 2026, 8:32 a.m. |
Created at: March 4, 2026, 7:28 p.m.