Triple
T11782700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vassouras branch |
E280188
|
entity |
| Predicate | hasClaimCharacteristic |
P274
|
FINISHED |
| Object | hereditary claim |
—
|
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: hereditary claim | Statement: [Vassouras branch, hasClaimCharacteristic, hereditary claim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClaimCharacteristic Context triple: [Vassouras branch, hasClaimCharacteristic, hereditary claim]
-
A.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
B.
hasClaimOn
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
-
C.
hasClaimType
Indicates that an entity is associated with or categorized under a specific type of claim.
-
D.
attributeClaim
Indicates that one entity asserts or specifies a particular attribute or property about another entity.
-
E.
hasClaimsOperationsIn
Indicates that an entity performs, manages, or is responsible for claims-related operations within a specified location, region, or organizational unit.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
Created at: April 8, 2026, 9:42 p.m.