Triple
T321283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archaea |
E6420
|
entity |
| Predicate | intronsInGenes |
P1393
|
FINISHED |
| Object | sometimes present |
—
|
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: sometimes present | Statement: [Archaea, intronsInGenes, sometimes present]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intronsInGenes Context triple: [Archaea, intronsInGenes, sometimes present]
-
A.
geneticMaterial
Indicates that one entity serves as the hereditary or genetic substance (e.g., DNA or RNA) of another entity.
-
B.
hasINSEECODE
Indicates that an entity is associated with a specific INSEE code, identifying it within the French national statistical and administrative system.
-
C.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
D.
EUAccession
Indicates that an entity becomes a member state of the European Union through the formal accession process.
-
E.
crossesBetween
Indicates that one entity passes from one side of a second entity to the other, traversing the space between two reference points or boundaries associated with that second entity.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea81a1e88190b3496070eb3d85f5 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e946607081909c8b97473aaf8d1b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.