Triple
T14361304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Will Reveal |
E356105
|
entity |
| Predicate | isPerformedByGroupType |
P99249
|
FINISHED |
| Object | family group |
—
|
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: family group | Statement: [Time Will Reveal, isPerformedByGroupType, family group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPerformedByGroupType Context triple: [Time Will Reveal, isPerformedByGroupType, family group]
-
A.
hasPerformerGroupType
chosen
Indicates that an entity is associated with a performer group of a specific type or category (e.g., band, choir, ensemble).
-
B.
appliedToGroupType
Indicates that something (such as a rule, setting, or action) is applied specifically to a particular type or category of group rather than to individual members.
-
C.
belongsToGroup
Indicates that an entity is a member of, or is included within, a particular group or collection.
-
D.
supportsGroupType
Indicates that one entity is compatible with or able to support a particular category or type of group.
-
E.
usesGroup
Indicates that an entity makes use of, operates with, or relies on a particular group as a collective resource, tool, or participant in some activity or process.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8f54bfb08190a27c0d12731acec2 |
completed | April 14, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:15 a.m.