Triple
T12625707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RF-101C |
E301507
|
entity |
| Predicate | cameraInstallation |
P17153
|
FINISHED |
| Object | nose-mounted cameras |
—
|
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: nose-mounted cameras | Statement: [RF-101C, cameraInstallation, nose-mounted cameras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameraInstallation Context triple: [RF-101C, cameraInstallation, nose-mounted cameras]
-
A.
typeOfInstallation
chosen
Indicates the specific kind or category of installation associated with an entity (e.g., how or in what form something is installed).
-
B.
bellMounting
Indicates that one entity is mounted, fixed, or installed as a bell onto another supporting structure or surface.
-
C.
overseesInstallation
Indicates that one entity is responsible for supervising and managing the process of installing another entity.
-
D.
installedInstrument
Indicates that one entity has placed or set up another entity as an instrument or device for use in a particular context or system.
-
E.
intendedInstallation
Indicates that one entity is meant or planned to be installed in, on, or as part of another entity or environment.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:14 p.m.