Triple
T32095669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eldar |
E819715
|
entity |
| Predicate | canBeRehoused |
P195505
|
FINISHED |
| Object | in new bodies by the Valar |
—
|
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: in new bodies by the Valar | Statement: [Eldar, canBeRehoused, in new bodies by the Valar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeRehoused Context triple: [Eldar, canBeRehoused, in new bodies by the Valar]
-
A.
canBeAdoptedBy
Indicates that one entity is eligible or allowed to be adopted by another entity.
-
B.
canBeVacated
Indicates that a position, status, or decision is capable of being annulled, set aside, or rendered void.
-
C.
canBeReconstituted
Indicates that something has the capacity to be restored or returned to a prior or functional state, typically after being separated, dissolved, or broken down.
-
D.
canBeVacant
Indicates that an entity (such as a position, property, or role) is capable of being unoccupied or without an assigned holder.
-
E.
canBeReorganizedBy
Indicates that one entity has the ability or authority to rearrange, restructure, or otherwise reorganize 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
| PDg | Predicate description generation | batch_69fdd5faea908190a17d77e050362ef5 |
completed | May 8, 2026, 12:24 p.m. |
Created at: May 1, 2026, 12:26 a.m.