Triple
T37565726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finduilas |
E933948
|
entity |
| Predicate | capturedOnOrdersOf |
P4712
|
FINISHED |
| Object | Glaurung |
—
|
NE NERFINISHED |
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: Glaurung | Statement: [Finduilas, capturedOnOrdersOf, Glaurung]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capturedOnOrdersOf Context triple: [Finduilas, capturedOnOrdersOf, Glaurung]
-
A.
capturedUnderCommandOf
Indicates that one entity was captured while operating under the authority, leadership, or command of another entity.
-
B.
commissionedUnderCommandOf
Indicates that an entity was formally authorized or initiated to act while under the authority or direction of a specific commanding entity.
-
C.
capturedBy
chosen
Indicates that one entity has been seized, taken into control, or otherwise apprehended by another entity.
-
D.
capturedFor
Indicates that one entity has been taken into custody, control, or possession specifically for the benefit, use, or purpose of another entity.
-
E.
commandeeredBy
Indicates that control or possession of something has been forcibly taken over by a particular agent or group.
- 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba61dff5081909fec88a7aeb0c8a1 |
completed | May 6, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69fba350e9a8819095893229d9643572 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.