Triple
T13130131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nahda |
E311947
|
entity |
| Predicate | hasKeyDomain |
P108220
|
FINISHED |
| Object | literature |
—
|
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: literature | Statement: [Nahda, hasKeyDomain, literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyDomain Context triple: [Nahda, hasKeyDomain, literature]
-
A.
hasKeyCapability
Indicates that an entity possesses an essential ability or function that is critical for performing a particular task or role.
-
B.
hasKeyElement
Indicates that one entity contains or depends on another entity that serves as a primary or essential component.
-
C.
hasKeyDocument
Indicates that an entity possesses or is associated with a primary or essential document relevant to a particular context or process.
-
D.
hasKeyFunction
Indicates that one entity serves as a primary or essential function or role for another entity.
-
E.
hasKeyState
Indicates that an entity possesses or is associated with a particular key-related status or condition (such as pressed, released, enabled, or disabled).
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819bfd348190a22d44f837877e1c |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98134df64819084a5674f9475dcc2 |
completed | April 10, 2026, 11:01 p.m. |
Created at: April 9, 2026, 9:07 p.m.