Triple
T34301812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karie |
E880200
|
entity |
| Predicate | indirectlyDerivedFrom |
P116509
|
FINISHED |
| Object | Caroline |
—
|
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: Caroline | Statement: [Karie, indirectlyDerivedFrom, Caroline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indirectlyDerivedFrom Context triple: [Karie, indirectlyDerivedFrom, Caroline]
-
A.
derivedFrom
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
B.
indirectOrigin
chosen
Indicates that one entity originates from or is derived through one or more intermediate sources or processes from another entity, rather than directly.
-
C.
derivedBy
Indicates that one entity is obtained, produced, or inferred from another through some transformation, process, or reasoning.
-
D.
indirectlyReplacedBy
Indicates that one entity has been superseded or taken over by another entity through one or more intermediate replacements, rather than by a direct, immediate substitution.
-
E.
inheritedFrom
Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:57 a.m.