Triple
T13130107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nahda |
E311947
|
entity |
| Predicate | hasStartApprox |
P48368
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Nahda, hasStartApprox, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStartApprox Context triple: [Nahda, hasStartApprox, early 19th century]
-
A.
hasApproximatePublicationStart
Indicates that an entity is associated with an estimated or imprecise starting date for its publication.
-
B.
timeStartApprox
chosen
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
C.
hasApproximateEnd
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
-
D.
hasApproximateUse
Indicates that one entity is used for a purpose that is similar to, but not exactly the same as, the use or function of another entity.
-
E.
hasApproximateOrigin
Indicates that an entity originates from a source or location that is known only approximately rather than precisely.
- 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_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. |
Created at: April 9, 2026, 9:07 p.m.