Triple
T33412918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bisnovat R-4 |
E855636
|
entity |
| Predicate | seekerPlacement |
P42883
|
FINISHED |
| Object | nose-mounted seeker |
—
|
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 seeker | Statement: [Bisnovat R-4, seekerPlacement, nose-mounted seeker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seekerPlacement Context triple: [Bisnovat R-4, seekerPlacement, nose-mounted seeker]
-
A.
positionSought
Indicates the specific role, job, or position that an entity is aiming to obtain or apply for.
-
B.
seeker
Indicates a relationship where one entity actively searches for, pursues, or attempts to obtain another entity or goal.
-
C.
placementIn
chosen
Indicates that one entity is located or positioned within the spatial or structural bounds of another entity.
-
D.
seekerType
Indicates the specific category or role of the entity that is performing or initiating the seeking action in the relationship.
-
E.
seeksLodgingIn
Indicates that one entity is actively trying to obtain or arrange a place to stay within a specified location.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e47f37848190aadb137c81760f1f |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.