Triple
T14421911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Chat |
E357603
|
entity |
| Predicate | visibilityDependsOn |
P8537
|
FINISHED |
| Object | amount paid |
—
|
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: amount paid | Statement: [Super Chat, visibilityDependsOn, amount paid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibilityDependsOn Context triple: [Super Chat, visibilityDependsOn, amount paid]
-
A.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
B.
visibilityRequirement
chosen
Indicates that one entity must be visible or perceivable under specified conditions for another entity, action, or rule to apply.
-
C.
observerDependent
Indicates that the truth, value, or manifestation of something varies depending on which observer is considering or measuring it.
-
D.
visibilityStatus
Indicates the current level or state of how observable, accessible, or exposed an entity is within a given context.
-
E.
representationDependsOn
Indicates that one representation is reliant on or derived from another representation in order to be valid, complete, or interpretable.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91102c3c81908f571a1fff3bdd47 |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.