Triple
T5912873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DPP |
E131503
|
entity |
| Predicate | bootstrappingMethod |
P67663
|
FINISHED |
| Object | QR code scan |
—
|
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: QR code scan | Statement: [DPP, bootstrappingMethod, QR code scan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bootstrappingMethod Context triple: [DPP, bootstrappingMethod, QR code scan]
-
A.
reconstructionMethod
Indicates the technique or process used to reconstruct, restore, or rebuild something from its original or fragmented state.
-
B.
weightingMethod
Indicates how relative importance or influence is assigned to elements within a set, such as criteria, features, or data points, in a calculation or decision process.
-
C.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
-
D.
boosterRecoveryMethod
Indicates the method or process used to recover a rocket booster after its mission.
-
E.
methodologicallyAssociatedWith
Indicates a relationship where two entities are connected through shared, related, or jointly applied methods, procedures, or methodological approaches.
- F. None of above. chosen
Provenance (4 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c048fc112c8190b905bf561c9de096 |
completed | March 22, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69c03352208c8190968efed05a9fd416 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c048fb02a081908e78629e1e283cd0 |
completed | March 22, 2026, 7:54 p.m. |
Created at: March 22, 2026, 3:59 p.m.