Triple
T8640827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erdős–Rényi model |
E204641
|
entity |
| Predicate | connectivityThreshold |
P84387
|
FINISHED |
| Object | p ≈ (log n)/n |
—
|
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: p ≈ (log n)/n | Statement: [Erdős–Rényi model, connectivityThreshold, p ≈ (log n)/n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectivityThreshold Context triple: [Erdős–Rényi model, connectivityThreshold, p ≈ (log n)/n]
-
A.
connectivity
Indicates...the existence, degree, or quality of a link or communication pathway between entities, allowing interaction or information flow between them.
-
B.
connectsWithin
Indicates that one entity establishes a connection or link between elements that lie inside the bounds or scope of another entity.
-
C.
connectivityFeatures
Indicates the types of network or communication options that are available or supported for connecting to or through an entity.
-
D.
connectsState
Indicates a relationship where one entity serves as a link or conduit between different states, conditions, or statuses of another entity.
-
E.
connectsUnder
Indicates that one entity forms a connection to another entity by passing beneath or under it.
- 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_69ca834ca1c88190a11ffb0200342fac |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc47944d1c819081f448f14d04bf9d |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc479284a8819099b0b0d879af3372 |
completed | March 31, 2026, 10:15 p.m. |
Created at: March 30, 2026, 6:28 p.m.