Triple
T2160537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Navy ratings |
E47990
|
entity |
| Predicate | canHoldAppointment |
P36074
|
FINISHED |
| Object | leading hand |
—
|
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: leading hand | Statement: [Royal Navy ratings, canHoldAppointment, leading hand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canHoldAppointment Context triple: [Royal Navy ratings, canHoldAppointment, leading hand]
-
A.
canConfirmAppointments
Indicates that an entity has the ability or permission to confirm scheduled appointments.
-
B.
openByAppointment
Indicates that access or availability is provided only at scheduled times arranged in advance, rather than during regular open hours.
-
C.
requiresForHeadAppointment
Indicates that a certain condition, qualification, or prior role must be fulfilled in order for an entity to be appointed as the head of something.
-
D.
isPersonalAppointment
Indicates that an appointment is scheduled for an individual’s personal matters rather than for professional, public, or organizational purposes.
-
E.
appointmentBy
Indicates that one entity is appointed or designated to a role, position, or task by another entity.
- 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe8894d481908eda9363fd36fea6 |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe1ecb7081909c2c66da08a48ab7 |
completed | March 7, 2026, 5:56 a.m. |
Created at: March 4, 2026, 7:45 p.m.