Triple
T16501057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AM |
E400799
|
entity |
| Predicate | carrierPropertyVaried |
P8159
|
FINISHED |
| Object | amplitude |
—
|
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: amplitude | Statement: [AM, carrierPropertyVaried, amplitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carrierPropertyVaried Context triple: [AM, carrierPropertyVaried, amplitude]
-
A.
basedOnCarrierType
Indicates that something is determined or defined according to the type or category of carrier involved.
-
B.
carrierOf
Indicates that one entity serves as the medium, vehicle, or host that contains, transports, or conveys another entity.
-
C.
alsoCarries
Indicates that an entity, in addition to other items or responsibilities it has, carries another specified item or load as well.
-
D.
transportCharacteristic
chosen
Indicates a relationship where a specific characteristic, property, or feature is attributed to a mode or instance of transport.
-
E.
associatedFlagCarrier
Indicates that one entity serves as the designated national or primary flag carrier airline associated with another entity (such as a country, region, or organization).
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e4ddc88819081fedb726add3e96 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.