Triple
T38447841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huorns |
E906687
|
entity |
| Predicate | sometimesGuidedBy |
P190922
|
FINISHED |
| Object | Ents |
—
|
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: Ents | Statement: [Huorns, sometimesGuidedBy, Ents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesGuidedBy Context triple: [Huorns, sometimesGuidedBy, Ents]
-
A.
sometimesEngageIn
Indicates that one entity engages in or performs an action or relationship with another entity on an occasional or intermittent basis, rather than consistently or always.
-
B.
sometimesTargetedIn
Indicates that an entity is occasionally, but not consistently, selected as the object or focus of a particular action, influence, or operation.
-
C.
sometimesExcludes
Indicates that one entity occasionally omits, leaves out, or does not include another entity under certain conditions or at certain times.
-
D.
sometimesHelps
Indicates that one entity provides help or assistance to another on some occasions but not consistently.
-
E.
sometimesIncluded
Indicates that one entity is occasionally, but not always, contained within, part of, or present in association with 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd34596288190b8e34a7a20b4c0db |
completed | May 7, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd31227708190a7df213597e66ca8 |
completed | May 7, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:31 p.m.