Triple
T5069944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Recess Records |
E114249
|
entity |
| Predicate | independent |
P8371
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Recess Records, independent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: independent Context triple: [Recess Records, independent, true]
-
A.
isIndependent
chosen
Indicates that an entity exists, functions, or operates without being controlled, influenced, or determined by another entity.
-
B.
independenceFrom
Indicates that one entity is not controlled, governed, or significantly influenced by another entity.
-
C.
originallyIndependentOf
Indicates that one entity was initially separate from, and not derived from or influenced by, another entity at the outset.
-
D.
independentlyFormulated
Indicates that multiple entities arrived at the same or similar idea, result, or formulation without influencing or relying on each other.
-
E.
independentRelease
Indicates that a work was released independently, without the backing or involvement of a major external organization or label.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd749f47908190891ac8432c5b5615 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.