Triple
T31975449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | For King & Country |
E816438
|
entity |
| Predicate | hasSiblingMemberRelationship |
P55387
|
FINISHED |
| Object | Joel Smallbone |
—
|
NE NERFINISHED |
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: Joel Smallbone | Statement: [For King & Country, hasSiblingMemberRelationship, Joel Smallbone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSiblingMemberRelationship Context triple: [For King & Country, hasSiblingMemberRelationship, Joel Smallbone]
-
A.
hasSiblingMembers
chosen
Indicates that two entities are members of a group or organization and are siblings to each other within that membership context.
-
B.
hasSisterRelationshipType
Indicates that there exists a sister-type familial relationship between the related entities.
-
C.
hasSuccessorMembers
Indicates that one set of members follows or replaces another set of members in a sequence, order, or organizational structure.
-
D.
hasMemberAlsoIn
Indicates that an entity has at least one member who also belongs to another specified group or collection.
-
E.
hasSiblingCollaboration
Indicates a collaborative relationship between two entities that are considered siblings within the same hierarchy or family.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 1, 2026, 12:11 a.m.