Triple
T11969349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern heritage movement |
E284873
|
entity |
| Predicate | hasSupporterClaim |
P4133
|
FINISHED |
| Object | focus on honoring ancestors |
—
|
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: focus on honoring ancestors | Statement: [Southern heritage movement, hasSupporterClaim, focus on honoring ancestors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupporterClaim Context triple: [Southern heritage movement, hasSupporterClaim, focus on honoring ancestors]
-
A.
hasSupporter
Indicates that one entity supports, endorses, or backs another entity.
-
B.
supportsClaim
chosen
Indicates that one entity provides evidence, reasoning, or backing that strengthens or validates the truth or credibility of another entity’s claim.
-
C.
hasClaimOn
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
-
D.
supportedClaimant
Indicates that one entity has provided assistance, backing, or advocacy in favor of another entity who is making a claim or seeking a benefit.
-
E.
hasSupporterGroup
Indicates that an entity is associated with a group of supporters that backs, promotes, or advocates for it.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037bee54819085242a3ef3e286f9 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:46 p.m.