Triple
T14427048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pMT1 |
E357722
|
entity |
| Predicate | carriersLocus |
P78758
|
FINISHED |
| Object | fra locus |
—
|
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: fra locus | Statement: [pMT1, carriersLocus, fra locus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriersLocus Context triple: [pMT1, carriersLocus, fra locus]
-
A.
isCarrierOf
Indicates that one entity serves as the bearer, holder, or transmitter of another entity (such as an object, substance, trait, or information).
-
B.
locusDescription
Indicates how the spatial position or location of an entity is described or characterized.
-
C.
hasGeneticLocus
chosen
Indicates that a genetic feature or trait is located at, or associated with, a specific position (locus) on a genome or chromosome.
-
D.
isMajorCarrierOf
Indicates that one entity serves as the primary or principal transporter or conveyor of another entity (such as goods, signals, or passengers).
-
E.
eligibleCarrier
Indicates that one entity is a valid or qualified carrier option for another entity under specified conditions.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de911398f08190be85bc0a8bef6b1b |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.