Triple
T28487627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REME |
E720874
|
entity |
| Predicate | hasCoreTask |
P46235
|
FINISHED |
| Object | field repairs |
—
|
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: field repairs | Statement: [REME, hasCoreTask, field repairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreTask Context triple: [REME, hasCoreTask, field repairs]
-
A.
hasCoreWork
chosen
Indicates that an entity possesses or is associated with a primary, central, or most essential piece of work or activity.
-
B.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
C.
hasCoreUnit
Indicates that an entity includes or is composed around a primary, central, or fundamental unit.
-
D.
hasCorePhase
Indicates that an entity possesses or is associated with a primary or central phase within a larger process or lifecycle.
-
E.
hasNumberOfTasks
Indicates that an entity is associated with a specific count of tasks.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
Created at: April 28, 2026, 2:59 a.m.