Triple
T22412952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algol |
E554036
|
entity |
| Predicate | massTransfer |
P67285
|
FINISHED |
| Object | occurs from Algol B to Algol A |
—
|
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: occurs from Algol B to Algol A | Statement: [Algol, massTransfer, occurs from Algol B to Algol A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massTransfer Context triple: [Algol, massTransfer, occurs from Algol B to Algol A]
-
A.
involvesParticleTransfer
Indicates that the relationship or action includes the movement or exchange of discrete particles from one entity to another.
-
B.
massBalance
Indicates that the total mass entering a system equals the total mass leaving or accumulating within it, reflecting conservation of mass.
-
C.
materialTransportedTo
Indicates that a material is moved or conveyed from one location or entity to another specified destination.
-
D.
materialTransportedFrom
chosen
Indicates that a material or substance is moved or carried from a specified source location to another place.
-
E.
energyTransferMethod
Indicates the process or mechanism by which energy is transferred from one entity or system to another.
- 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_69e11e4e6ce8819085a1e06d886bf21c |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1594496348190ba25dc0193d092f2 |
completed | April 29, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.